| 3 | Approval of the Agenda | |
|---|---|---|
| R3-205900 | RAN3#110-e Meeting Agenda | Chairman |
| 4 | Approval of the minutes from previous meetings | |
| R3-205901 | RAN3#109-e Meeting report | ETSI-MCC |
| R3-206937 | RAN3#109-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-206422 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-206429 | List of E-mail Discussions | RAN3 Chairman |
| 8.1 | New Incoming LSs | |
| R3-205911 | LS on mandatory support of full rate user plane integrity protection for 5G | CT WG1 |
| R3-205912 | LS on handling OVERLOAD START message in the N3IWF | CT WG1 |
| R3-205913 | LS on End marker in NG-RAN initiated QoS Flow mobility | CT WG4 |
| R3-205914 | Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN WG1 |
| R3-205915 | LS on Latency of NR Positioning Protocols | RAN WG1 |
| R3-205916 | Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | RAN WG2 |
| R3-205917 | LS Reply on SA WG2 assumptions on architecture aspects for using satellite access in 5G | RAN WG2 |
| R3-205918 | Reply LS on early UE capability retrieval for eMTC | RAN WG2 |
| R3-205919 | Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G | RAN WG2 |
| R3-205920 | Reply LS on RAN impact of FS_5MBS Study | TSG RAN |
| R3-205921 | Reply LS on NG-RAN behaviour upon AMF triggered changes of the MRL for PNI-NPN | SA WG2 |
| R3-205924 | LS on System support for Multi-USIM devices | SA WG2 |
| R3-205926 | LS on mandatory support of full rate user plane integrity protection for 5G | SA WG2 |
| R3-205927 | Reply LS on addition of the Pending Data Indication to 5GS | SA WG2 |
| R3-205928 | Reply LS on system support for WUS | SA WG2 |
| R3-205929 | Reply LS on assistance indication for WUS | SA WG2 |
| R3-205930 | LS on Cell Configuration within TA/RA to Support Allowed NSSAI | SA WG2 |
| R3-205932 | LS reply to LS on M.resm-AI “Requirements for energy saving management of 5G RAN system with AI” | SA WG5 |
| R3-205935 | Reply LS on RAN impact of FS_5MBS Study | TSG SA |
| R3-205965 | Correction of End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-205966 | Reply LS on End Marker in NG-RAN initiated QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-205967 | Correction of DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-205968 | Correction of DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-205969 | RAN3 feedback related to MUSIM feature | Nokia, Nokia Shanghai Bell |
| R3-205970 | Reply LS on System Support for multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-205973 | Cell Configuration with TA for allowed NSSAI | Nokia, Nokia Shanghai Bell |
| R3-205974 | Reply LS for cell configuration within TA/RA to support Allowed NSSAI | Nokia, Nokia Shanghai Bell |
| R3-205983 | CR38413 for clarication of AS rekeying handling in Rel-15 | ZTE |
| R3-205984 | CR38413 for clarication of AS rekeying handling in Rel-16 | ZTE |
| R3-205985 | Discussion on support for Multi-USIM devices | ZTE |
| R3-205986 | [Draft] Reply LS on System support for Multi-USIM devices | ZTE |
| R3-205987 | BLCR36413 for support for Multi-USIM devices | ZTE |
| R3-205988 | BLCR38413 for support for Multi-USIM devices | ZTE |
| R3-205989 | BLCR38423 for support for Multi-USIM devices | ZTE |
| R3-206061 | SRS-RSRP configuration for CLI | Nokia, Nokia Shanghai Bell, China Telecom, Orange, LGE, ZTE |
| R3-206073 | SRS-RSRP configuration for CLI | LGE, China Telecom, Orange, Nokia, Nokia Shanghai Bell, ZTE |
| R3-206119 | Inclusion of Extended Connected Time | Huawei |
| R3-206120 | Discussion on End Marker in NG-RAN initiated QoS Flow mobility | Huawei |
| R3-206121 | [Draft] Reply LS on End marker in NG-RAN initiated QoS Flow mobility | Huawei |
| R3-206122 | End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading | Huawei, Deutsche Telekom |
| R3-206123 | End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading | Huawei, Deutsche Telekom |
| R3-206164 | On the use of the Extended Connected Time IE | Qualcomm Incorporated |
| R3-206165 | Correction of usage of the Extended Connected Time | Qualcomm Incorporated |
| R3-206166 | Support of release on CAG subscription change | Qualcomm Incorporated |
| R3-206167 | Support of release on CAG subscription change | Qualcomm Incorporated |
| R3-206168 | On Cell Configuration within TA/RA to Support Allowed NSSAI | Qualcomm Incorporated |
| R3-206169 | [DRAFT] Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI | Qualcomm Incorporated |
| R3-206280 | DRAFT Reply LS on System support for Multi-USIM devices | vivo |
| R3-206281 | Discussion on Multi-SIM devices solutions | vivo |
| R3-206348 | Consideration on allowed PNI-NPN changed | ZTE Corporation |
| R3-206350 | CR38.300 for allowed PNI-NPN changed | ZTE Corporation |
| R3-206365 | CR38.413 for allowed PNI-NPN changed | ZTE Corporation |
| R3-206443 | Introducing QoS parameters update at Xn handover | Huawei |
| R3-206444 | Introducing QoS parameters update at Xn handover | Huawei |
| R3-206445 | Discussion on Cell Configuration within TA/RA to Support Allowed NSSAI | Huawei |
| R3-206446 | [Draft] Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI | Huawei |
| R3-206447 | Handling OVERLOAD START message in the N3IWF | Huawei |
| R3-206448 | Handling OVERLOAD START message in the N3IWF | Huawei |
| R3-206449 | Handling OVERLOAD START message in the N3IWF | Huawei |
| R3-206450 | Discussion on support of Multi-USIM devices | Huawei |
| R3-206500 | Handling of End marker during QoS Flow mobility | Ericsson |
| R3-206501 | [DRAFT] Reply LS on End marker in NG-RAN initiated QoS Flow mobility | Ericsson |
| R3-206502 | Introduction of End Marker handling in stage-2 | Ericsson |
| R3-206503 | Introduction of End Marker handling in stage-2 | Ericsson |
| R3-206540 | Analysis of slice availability principle | Ericsson |
| R3-206541 | Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI | Ericsson |
| R3-206552 | SA2 LS on Multi-USIM devices | Qualcomm Incorporated |
| R3-206553 | [DRAFT] Reply LS on System support for Multi-USIM devices | Qualcomm Incorporated |
| R3-206566 | Response to SA2 LS S2-2006037: Paging Repetition in RAN aspects | VODAFONE Group Plc |
| R3-206569 | Reply LS to RAN3 for clarification of QoS Parameters Update at Xn Handover | SA WG2 |
| R3-206570 | Addition of Extended Connected Time to NG-AP | Ericsson |
| R3-206571 | Addition of Extended Connected Time to NG-AP | Ericsson |
| R3-206572 | Addition of Extended Connected Time to NG-AP | Ericsson |
| R3-206573 | [DRAFT] LS reply on addition of Extended Connected Time to 5GS | Ericsson |
| R3-206601 | [DRAFT] Reply LS on clarification of QoS Parameters Update at Xn Handover | Ericsson |
| R3-206602 | QoS Parameters Update at Xn Handover | Ericsson |
| R3-206603 | QoS Parameters Update at Xn Handover | Ericsson |
| R3-206604 | Discussion on System support for Multi-USIM devices | Ericsson |
| R3-206605 | [DRAFT] Reply LS on System support for Multi-USIM devices | Ericsson |
| R3-206616 | Discussion on handling OVERLOAD START message in the N3IWF | Ericsson |
| R3-206722 | Response to R3-205930 Cell Configuration within TA/RA to Support Allowed NSSAI | ZTE |
| R3-206723 | Response LS related to SRS-RSRP configuration for CLI | ZTE, Nokia, Nokia Shanghai Bell, LGE,China Mobile |
| R3-206790 | Cell configuration within TARA to support allowed NSSAI | CMCC |
| R3-206791 | Reply LS on cell configuration within TARA to support allowed NSSAI | CMCC |
| R3-206836 | LS on Cell Configuration within TA/RA to Support Allowed NSSAI | CT WG1 |
| R3-206837 | Reply to LS S2-2006037 on System support for Multi-USIM devices | SA WG3 |
| R3-206839 | LS on Use of Survival Time for Deterministic Applications in 5GS | SA WG2 |
| R3-206869 | Development of a draft new Report ITU-R M.[IMT.C-V2X] – The use of the terrestrial component of IMT systems for Cellular-Vehicle-to-Everything | ITU-R WP 5D |
| R3-206870 | LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS - Future Technology Trends for the evolution of IMT towards 2030 and beyond | ITU-R WP 5D |
| R3-206871 | Response to R3-206567 | Ericsson |
| R3-206919 | LS on QoE Measurement Collection | SA WG5 |
| R3-206920 | Reply LS on URI for streaming trace reporting in LTE | SA WG5 |
| R3-206921 | Reply LS on energy efficiency | SA WG5 |
| R3-206924 | CB: #70_USIM_support - summary of email discussion | Vivo-moderator |
| R3-206925 | CB: #71_CellConfig_AllowedNSSAI - Summary of email discussion | Nokia - moderator |
| R3-206926 | CB: #72_EndMarker_QoSflowMob - Summary of email discussion | Huawei - moderator |
| R3-206927 | CB: # 73_SRS-RSRPinfoXchg - Summary of email discussion | ZTE - moderator |
| R3-206928 | CB: # 74_PendingDataIndication - Summary of email discussion | Qualcomm - moderator |
| R3-206929 | CB: # 75_QoSupdate_XnHO - summary of email discussion | Ericsson - moderator |
| R3-206930 | CB: # 77_SurvivalTimeDeterministicApps - Summary of email discussion | Nokia - moderator |
| R3-206931 | [draft] Reply LS on Use of Survival Time for Deterministic Applications in 5GS | Nokia |
| R3-206932 | CB: # 78_PNI-NPN - Summary of email discussion | Qualcomm |
| R3-206936 | CB: # 76_OverloadN3IWF - Summary of email discussion | Huawei - moderator |
| R3-206938 | Reply LS on NG-RAN behaviour upon AMF triggered changes of the MRL for PNI-NPN | SA WG2 |
| R3-206972 | QoS Parameters Update at Xn Handover | Ericsson, Samgung, Huawei |
| R3-207047 | End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-207048 | End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading | Huawei, Deutsche Telekom |
| R3-207085 | Reply LS on End Marker in NG-RAN initiated QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-207086 | Correction of DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-207087 | Correction of DL End markers and QoS Flow Mobility | Nokia, Nokia Shanghai Bell |
| R3-207089 | Introducing QoS parameters update at Xn handover | Huawei, Huawei, Ericsson, Samsung |
| R3-207102 | Handling OVERLOAD START message in the N3IWF | Huawei |
| R3-207122 | Support of release on CAG subscription change | Qualcomm Incorporated |
| R3-207123 | Correction of usage of the Extended Connected Time | Qualcomm Incorporated, Ericsson, ZTE |
| R3-207125 | DRAFT Reply LS on System support for Multi-USIM devices | vivo |
| R3-207147 | Reply LS for cell configuration within TA/RA to support Allowed NSSAI | Nokia, Nokia Shanghai Bell |
| R3-207178 | Correction of usage of the Extended Connected Time | Qualcomm Incorporated, Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-207179 | Support of release on CAG subscription change | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-207180 | Support of release on CAG subscription change | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-207188 | [DRAFT] Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI | Qualcomm Incorporated |
| R3-207200 | CLI Notification between NG-RAN node | ZTE |
| R3-207207 | Reply LS on System support for Multi-USIM devices | vivo |
| R3-207211 | Reply LS on Use of Survival Time for Deterministic Applications in 5GS | Nokia |
| 8.2 | LSin received during the meeting | |
| R3-207011 | Reply LS on full slot formats support in TDD UL-DL | RAN WG1 |
| R3-207042 | Reply LS on Latency of NR Positioning Protocols | RAN WG2 |
| R3-207109 | Reply LS on updated Rel-16 LTE and NR parameter lists | RAN WG2 |
| R3-207140 | Reply LS on Latency of NR Positioning Protocols | Huawei |
| 8.3.1 | QoS Monitoring for URLLC | |
| R3-206093 | Introduction of D1 measuremnt tranfer on E1AP | Huawei |
| R3-206377 | On RAN support for QoS monitoring using GTP-U path | Nokia, Nokia Shanghai Bell |
| R3-206378 | N3/N9 packet delay reporting for QoS monitoring using GTP-U path | Nokia, Nokia Shanghai Bell |
| R3-206379 | Activation of N3 packet delay reporting for QoS monitoring using GTP-U path | Nokia, Nokia Shanghai Bell |
| R3-206380 | Activation of N3 packet delay reporting for QoS monitoring using GTP-U path | Nokia, Nokia Shanghai Bell |
| R3-206423 | Discussion on LS on Clarification on URLLC QoS Monitoring | Huawei |
| R3-206424 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-206425 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-206426 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-206427 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-206545 | Reply LS on QoS Monitoring for URLLC | Ericsson |
| R3-206546 | NR QoS Monitoring | Ericsson |
| R3-206838 | LS on Clarification on URLLC QoS Monitoring | SA WG2 |
| R3-206844 | CB: # 1_QoSmonURLLC - Summary of email discussion | Nokia - moderator |
| R3-207074 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-207075 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-207076 | Introduction of reporting frequency for Qos monitoring for URLLC | Huawei |
| R3-207077 | Introduction of D1 measurement transfer on E1AP | Huawei |
| R3-207111 | N3/N9 packet delay reporting for QoS monitoring using GTP-U path | Nokia, Nokia Shanghai Bell |
| R3-207156 | Reply on LS on Clarification on URLLC QoS Monitoring | Huawei |
| R3-207177 | Reply LS on QoS Monitoring for URLLC | Ericsson |
| 8.3.2 | Handover to Congested Cells | |
| R3-205975 | Alternative QoS Profiles and handover to congested sites | Nokia, Nokia Shanghai Bell |
| R3-205976 | Response LS on HO to congested cells | Nokia, Nokia Shanghai Bell |
| R3-206458 | Further discussions on AQP | Huawei, Orange, BT |
| R3-206459 | Clarification of AQP | Huawei, Orange, BT |
| R3-206460 | [DRAFT] Reply LS on HO to congested cells | Huawei, Orange, BT |
| R3-206574 | How to address the handover to congested cells | Ericsson |
| R3-206575 | Addition of Queuing Indicator over NG-AP Handover message | Ericsson |
| R3-206576 | Addition of Queuing Indicator over Xn-AP Handover message | Ericsson |
| R3-206577 | [DRAFT] LS on addition of queuing indicator for HO to congested cells | Ericsson |
| R3-206845 | CB: # 2_HO_congested_cells - Summary of email discussion | Ericsson - moderator |
| R3-207044 | [DRAFT] LS on addition of queuing indicator for HO to congested cells | Ericsson |
| R3-207091 | Clarification of AQP | Huawei, Orange, BT |
| R3-207182 | LS on addition of queuing indicator for HO to congested cells | Ericsson |
| 9.2.1 | Reporting of SFN Time Difference in LPPa | |
| R3-206159 | Assistance data for OTDOA | Qualcomm Incorporated |
| R3-206160 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated |
| R3-206161 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated |
| R3-206578 | Reporting of SFN time difference for OTDOA | Ericsson, NTT DOCOMO |
| R3-206579 | Reporting of SFTD measurements in LPPa | Ericsson, NTT DOCOMO |
| R3-206580 | Reporting of SFTD measurements in LPPa | Ericsson, NTT DOCOMO |
| R3-206581 | Reporting of SFTD measurements in NRPPa | Ericsson |
| R3-206582 | Reporting of SFTD measurements in NRPPa | Ericsson |
| R3-206583 | [DRAFT] LS on addition of SFN time difference reporting | Ericsson |
| R3-206846 | CB: # 3_SFNtime_difference_LPPa - Summary of email discussion | Ericsson - moderator |
| R3-207009 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated, Ericsson |
| R3-207010 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated, Ericsson |
| R3-207173 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated, Ericsson |
| R3-207174 | Support OTDOA assistance data for case of NR serving cell | Qualcomm Incorporated, Ericsson |
| R3-207175 | CB: # 3_SFNtime_difference_LPPa - Summary of email discussion | Ericsson - moderator |
| 9.2.2 | Others | |
| R3-206110 | Consideration on immediate suspension | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-206111 | Correction on immediate suspension | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-206112 | NPRACH configuration exchanging | Huawei, CMCC |
| R3-206113 | Exchanging of NB-IoT RLF report | Huawei, CMCC |
| R3-206114 | Exchanging of NB-IoT RLF report | Huawei, CMCC |
| R3-206115 | Correction on Coverage Enhancement Restrictions | Huawei, China Telecom |
| R3-206117 | Correction on RAT Information handling | Huawei, Vodafone, CMCC, Deutsche Telekom, BT, China Telecom |
| R3-206118 | Correctoin of the RAT Type Handling | Huawei, Vodafone, CMCC, Deutsche Telekom, BT, China Telecom |
| R3-206162 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Incorporated |
| R3-206547 | Synching the Collection Period values to those specified in TS32.422 | Ericsson |
| R3-206548 | Synching the Collection Period values to those specified in TS32.422 | Ericsson |
| R3-206933 | CB: # 79_ImmediateSuspension - Summary of email discussion | Huawei - moderator |
| R3-206945 | CB: # 80_NPRACHconfigXch - Summary of email discussion | Huawei - moderator |
| R3-206946 | CB: # 81_RATtypeHandling - Summary of email discussion | Huawei - moderator |
| R3-206947 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Incorporated |
| R3-206948 | CB: # 82_MDTCollectionPeriodValues - Summary of email discussion | Ericsson - moderator |
| R3-206984 | Correction on immediate suspension | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE |
| R3-207067 | [DRAFT] LS to SA2 on Immediate Suspension | ZTE |
| R3-207071 | [DRAFT] LS to SA2 on Immediate Suspension | ZTE |
| R3-207088 | Correction on immediate suspension | Huawei |
| R3-207099 | NPRACH configuration exchanging | Huawei, CMCC, Ericsson, ZTE |
| R3-207137 | Correction on immediate suspension | Huawei, Qualcomm Incorporated |
| R3-207138 | LS to SA2 on Immediate Suspension | ZTE |
| R3-207149 | LS to SA5 on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-207214 | LS to SA5 on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-207215 | LS to SA5 on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R3-207222 | LS to SA5 on MDT Stage 2 and Stage 3 alignment | Ericsson |
| 9.3.1 | NAS Non-Delivery | |
| R3-205977 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-205978 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-205979 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-205980 | Response LS on NAS NON Delivery for RRC INACTIVE State | Nokia, Nokia Shanghai Bell, Oarnge |
| R3-206074 | Discussion on NAS non delivery | ZTE Corporation |
| R3-206075 | Correction on NAS non delivery over NG | ZTE Corporation |
| R3-206077 | Correction on NAS non delivery over NG | ZTE Corporation |
| R3-206078 | Response LS on NAS Non Delivery for RRC_INACTIVE state | ZTE Corporation |
| R3-206211 | NAS PDU non delivery | Ericsson |
| R3-206212 | NAS PDU handling | Ericsson |
| R3-206213 | NAS PDU handling | Ericsson |
| R3-206214 | NAS PDU handling | Ericsson |
| R3-206215 | NAS PDU handling | Ericsson |
| R3-206272 | Correction of NAS Non Delivery Indication | CATT |
| R3-206273 | Correction to NAS Non Delivery Indication_NGAP Rel-15 | CATT |
| R3-206274 | Correction to NAS Non Delivery Indication_NGAP Rel-16 | CATT |
| R3-206439 | Further discussion on NAS Non-Delivery | Huawei |
| R3-206440 | Further discussion on NAS Non-Delivery | Huawei |
| R3-206441 | Further discussion on NAS Non-Delivery | Huawei |
| R3-206442 | [Draft] Reply LS on NAS Non delivery | Huawei |
| R3-206606 | Draft] Reply LS on NAS Non delivery for RRC Inactive state | Ericsson |
| R3-206847 | CB: # 4_NASnon_delivery - Summary of email discussion | CATT - moderator |
| R3-207080 | Reply LS on NAS Non delivery for RRC_INACTIVE state | CATT |
| R3-207170 | Reply LS on NAS Non delivery for RRC_INACTIVE state | CATT |
| 9.3.2 | Overlapping Band Handling in F1AP | |
| R3-206086 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-206087 | Correction on Overlapping Band Handling over F1 | ZTE, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-206216 | Overlapping bands handling | Ericsson, Verizon Wireless |
| R3-206217 | Overlapping band handling CR 38.473 | Ericsson, Verizon Wireless |
| R3-206218 | Overlapping band handling CR 38.473 | Ericsson, Verizon Wireless |
| R3-206848 | CB: # 5_OverlappingBand_F1AP - Summary of email discussion | ZTE - moderator |
| 9.3.3 | AS-Rekey and Emergency Fallback | |
| R3-205923 | Reply LS on AS rekeying handling | SA WG2 |
| R3-206108 | Correction on AS-rekey and Emergency fallback | Huawei, Nokia, Nokia Shanghao Bell, Deutsche Telekom |
| R3-206109 | Correction on AS-rekey and Emergency fallback | Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-206220 | AS re-keying and Emergency Fallback in the UE Context Modification procedure | Ericsson |
| R3-206222 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-206224 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-206267 | Discussion on AS rekey and Emergency fallback | CATT |
| R3-206268 | Correction on collision of AS-rekey and Emergency fallback_NGAP CR_set1 Rel-15 | CATT |
| R3-206269 | Correction on collision of AS-rekey and Emergency fallback_NGAP CR_set1 Rel-16 | CATT |
| R3-206270 | Correction on collision of AS-rekey and Emergency fallback_NGAP CR_set2 Rel-15 | CATT |
| R3-206271 | Correction on collision of AS-rekey and Emergency fallback_NGAP CR_set2 Rel-16 | CATT |
| R3-206607 | Draft] Reply LS on AS rekeying handling | Ericsson |
| R3-206653 | CR38413 for clarication of AS rekeying handling in Rel-15 | ZTE |
| R3-206654 | CR38413 for clarication of AS rekeying handling in Rel-16 | ZTE |
| R3-206849 | CB: # 6_AS_rekey_emergency_fallback - Summary of email discussion | Huawei - moderator |
| R3-206970 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-206971 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-207121 | [Draft] Reply LS on AS rekeying handling | Huawei |
| 9.3.4 | Direct Data Forwarding Between NG-RAN and E-UTRAN | |
| R3-205936 | CR to TS38.463 on Support of direct data forwarding for inter-system HO | China Telecom, Samsung, CATT,Nokia , Nokia Shanghai Bell, ZTE, Lenovo , Motorola Mobility, Huawei |
| R3-205946 | Enabling direct data forwarding for inter-RAT HO with SN-terminated bearers | Nokia, Nokia Shanghai Bell |
| R3-206015 | Direct data forwarding for inter-system HO from 4G to 5G with a shared split (S)gNB | Samsung |
| R3-206016 | Support of direct data forwarding for inter-system HO from 4G to 5G with a shared split (S)gNB | Samsung |
| R3-206182 | SN direct data forwarding | Qualcomm Incorporated, CATT, China Telecom |
| R3-206183 | SN direct data forwarding | Qualcomm Incorporated, CATT, China Telecom |
| R3-206219 | Support of Direct Data Forwarding for Inter-System Handover | Nokia, Nokia Shanghai Bell, CATT, China Telecom, ZTE, Lenovo, Huawei |
| R3-206221 | Correction of direct forwarding for inter-system handover | Nokia, Nokia Shanghai Bell |
| R3-206330 | Support of direct data forwarding for inter-system HO | CATT,China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-206331 | Support of inter-node handover with a shared split (S)gNB | CATT,China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-206619 | Inter-system direct data forwarding and E1 | Ericsson |
| R3-206620 | Inter-system direct data forwarding and E1 | Ericsson |
| R3-206627 | PDCP SN issue for EPC to 5GC handover | Huawei |
| R3-206628 | PDCP SN issue for EPC to 5GC handover | Huawei |
| R3-206673 | Discussion on inter-system handover from EN-DC to SA | CATT, China Telecom,Qualcomm, CMCC |
| R3-206675 | CR for 36.423 Support of direct data forwarding for EN-DC to SA | CATT, China Telecom |
| R3-206677 | CR to 38.423 on Support of direct data forwarding for S-NG-RAN node change or NR-NR DC to SA handover | China Telecom,CATT |
| R3-206679 | CR to 38.463 on Support of direct data forwarding for inter-system HO | China Telecom, CATT,Nokia , Nokia Shanghai Bell, ZTE |
| R3-206850 | CB: # 7_DirectDataFwd_E1 - Summary of email discussion | CATT - moderator |
| R3-206851 | CB: # 8_DirectDataFwd_DC-SAmobility - Summary of email discussion | Qualcomm - moderator |
| R3-206949 | CB: # 83_DirectFwding - Summary of email discussion | Nokia - moderator |
| R3-206950 | CB: # 84_PDCP_SN_correction - Summary of email discussion | Huawei - moderator |
| R3-206951 | PDCP SN issue for EPC to 5GC handover | Huawei |
| R3-206952 | PDCP SN issue for EPC to 5GC handover | Huawei |
| R3-207183 | CR to TS38.463 on Support of direct data forwarding for inter-system HO | China Telecom, Samsung, CATT,Nokia , Nokia Shanghai Bell, ZTE, Lenovo , Motorola Mobility, Huawei |
| 9.3.5 | MDT for Inactive UEs | |
| R3-206032 | Discussion on the MDT for inactive UE | Samsung |
| R3-206033 | Support the feature that management based logged MDT doesn’t overwrite signalling based logged MDT | Samsung |
| R3-206034 | Support the feature that management based logged MDT doesn’t overwrite signalling based logged MDT | Samsung |
| R3-206094 | Further discussion on MDT configuration overriding issue | Huawei |
| R3-206095 | [DRAFT] LS on management based MDT configuration not overwriting signalling based MDT configuration | Huawei |
| R3-206549 | Discussion on Signalling and Management based Logged MDT | Ericsson |
| R3-206550 | Draft LS on UE based solution related to Logged MDT | Ericsson |
| R3-206701 | Management based MDT should not overwrite signaling based MDT | ZTE |
| R3-206702 | NGAP management based MDT should not overwrite signaling based MDT | ZTE |
| R3-206703 | XnAP management based MDT should not overwrite signaling based MDT | ZTE |
| R3-206704 | LS-out management based MDT should not overwrite signaling based MDT | ZTE |
| R3-206852 | CB: # 9_MDT_inactiveUEs - Summary of email discussion | Ericsson - moderator |
| R3-207148 | Draft LS on UE based solution related to Logged MDT | Ericsson |
| R3-207176 | LS on UE based solution related to Logged MDT | Ericsson |
| 9.3.6 | Redundant Tunnel Setup | |
| R3-206223 | Correction of Redundant Tunnel Setup | Nokia, Nokia Shanghai Bell |
| R3-206225 | Correction of Redundant Tunnel Setup | Nokia, Nokia Shanghai Bell |
| R3-206608 | Discussion on Redundant Tunnel Setup | Ericsson |
| R3-206609 | Redundant Tunnel Setup | Ericsson |
| R3-206610 | Including the Redundant UL NG-U UP TNL Information in the Modify Request | Ericsson |
| R3-206629 | Discussion on Redundant Tunnel Setup over NG | Huawei |
| R3-206853 | CB: # 10_RedundantTunnelSetup - Summary of email discussion | Nokia - moderator |
| R3-207084 | Correction of Redundant Tunnel Setup | Nokia, Nokia Shanghai Bell |
| 9.3.7 | Others | |
| R3-206505 | Removal of duplicated imports | Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-206611 | XnAP Rapporteur CR | Ericsson |
| R3-206612 | XnAP Rapporteur CR | Ericsson |
| R3-206944 | Removal of duplicated imports | Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-206953 | XnAP Rapporteur CR | Ericsson |
| R3-206954 | XnAP Rapporteur CR | Ericsson |
| 9.3.7.1 | Other Corrections | |
| R3-205902 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-205903 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-205922 | Non-Monotonic Alternative QoS Parameter values | VODAFONE Group Plc |
| R3-205937 | Discussion on the LTE-NR Relative Timing Indication over X2/Xn | China Telecom, Qualcomm Incorporated, ZTE,CATT |
| R3-205938 | CR to TS36.423 on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE,CATT |
| R3-205939 | Correction on V2X related information | Google Inc., Ericsson |
| R3-205941 | Correction on CPC Complete Transfer | Google Inc., NEC, Samsung, CATT |
| R3-205942 | Correction on CPC Complete Transfer | Google Inc., NEC, Samsung, CATT |
| R3-205943 | Correction on CPC Complete Transfer | Google Inc., NEC, Samsung, CATT |
| R3-205945 | Correction on DSCP Derivation in IAB-donor node | Perspecta Labs Inc., CISA ECD, AT&T |
| R3-205994 | Correction on F1-C transfer in Rel-16 IAB | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
| R3-205995 | CR on F1-C transfer for Rel-16 IAB | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
| R3-205996 | Correction on transmission stop for Rel-16 DAPS | Samsung |
| R3-205997 | CR on transmission stop for Rel-16 DAPS | Samsung |
| R3-206005 | Lossless intra-system HO in disaggregate gNB scenario | Samsung, Huawei, China Telecom, LGU+ |
| R3-206006 | Correction of intra-system HO in CP-UP seperation scenario | Samsung, Huawei, China Telecom, LGU+ |
| R3-206007 | Correction of intra-system HO in CP-UP seperation scenario | Samsung, Huawei, China Telecom, LGU+ |
| R3-206008 | Open issue for Intra-system HO in case of full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility |
| R3-206009 | Correction of Intra-system HO for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility |
| R3-206010 | Correction of Intra-system HO for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility |
| R3-206011 | Correction of Intra-system HO data forwarding for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility |
| R3-206012 | Correction of Intra-system HO data forwarding for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility |
| R3-206024 | Correction of S-NODE MODIFICATION REQUEST ACKNOWLEDGE message | Samsung |
| R3-206025 | orrection of S-NODE MODIFICATION REQUEST ACKNOWLEDGE message | Samsung |
| R3-206026 | orrection of S-NODE MODIFICATION REQUEST ACKNOWLEDGE message | Samsung |
| R3-206054 | Futher discussion on NR SCG release for UE power saving | ZTE, NEC, China Telecom |
| R3-206055 | CR36423 for NR SCG release for power saving | ZTE, NEC, China Telecom |
| R3-206056 | CR38423 for NR SCG release for power saving | ZTE, NEC, China Telecom |
| R3-206069 | Clarification on TAI Slice Support List | China Telecommunications |
| R3-206070 | Clarification on TAI Slice Support List | China Telecommunications |
| R3-206071 | Clarification on TAI Slice Support List | China Telecommunications |
| R3-206088 | Discussion on One PDU session with Multiple CU-UPs | ZTE Corporation, China Telecom, CATT |
| R3-206089 | Support one PDU session with multiple CU-UPs for TS38.401 | ZTE Corporation, China Telecom, CATT |
| R3-206090 | Support one PDU session with multiple CU-UPs for TS38.413 | ZTE Corporation, China Telecom, CATT |
| R3-206116 | Correction of SN modification request ack message-set 2 | Samsung R&D Institute UK |
| R3-206124 | Correction of SN modification request ack message-set 2 | Samsung R&D Institute UK |
| R3-206125 | Correction on Radio Resource Status Metric | CATT |
| R3-206126 | Correction on PRACH coordination | CATT |
| R3-206127 | Correction on LTE UE RLF Report | CATT |
| R3-206128 | Correction on UE History Information | CATT |
| R3-206129 | Discussion on MRO for RRC re-connected cell | CATT |
| R3-206130 | Correction on inconsistent description for attempted and successful re-connected cell | CATT |
| R3-206131 | Clarification on trigger condition for trace Failure Indication procedure | CATT |
| R3-206132 | Clarification on multiple Trace Start procedure | CATT |
| R3-206150 | UL Configuration handling in MR-DC | NEC |
| R3-206151 | Correction on UL Configuration handling | NEC |
| R3-206152 | Correction on UL Configuration handling | NEC |
| R3-206153 | Correction fast MCG recovery in RRC Transfer procedure | NEC |
| R3-206154 | Correction of IAB related RRC Container in RRC TRANSFER message | NEC |
| R3-206163 | Correction of F1AP positioning procedures | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-206180 | Inter MN resume without SN change | Qualcomm Incorporated |
| R3-206181 | Inter MN resume without SN change (CR to 38.423) | Qualcomm Incorporated |
| R3-206199 | Further correction on broadcast PLMN information on F1 | Nokia, Nokia Shanghai Bell |
| R3-206200 | Further correction on PLMN info in Served Cell Information IE | Nokia, Nokia Shanghai Bell |
| R3-206201 | Further correction on PLMN info in Served Cell Information IE | Nokia, Nokia Shanghai Bell |
| R3-206202 | Removal of duplicate import | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-206203 | Mobility Restrictions in S-Node Addition procedure | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-206204 | Introduction of 5GC Mobility Restriction List Container IE in S-Node Addition | Nokia, Nokia Shanghai Bell |
| R3-206205 | Corrections to tabular and asn.1 for NR positioning (NRPPa) | Nokia, Nokia Shanghai Bell |
| R3-206206 | Corrections to tabular and asn.1 for NR positioning (F1AP) | Nokia, Nokia Shanghai Bell |
| R3-206226 | Correction of UE Release Request | Nokia, Nokia Shanghai Bell, Orange |
| R3-206227 | Enabling usage of flexible NG-RAN Node ID length | Ericsson, Verizon Wireless |
| R3-206228 | Correction of UE Release Request | Nokia, Nokia Shanghai Bell, Orange |
| R3-206229 | Draft LS on broadcasting gNB ID length in system information block | Ericsson, Verizon Wireless |
| R3-206230 | Correction of UE Release Request | Nokia, Nokia Shanghai Bell, Orange |
| R3-206231 | Corrections of procedures for PWS tests | Ericsson, One2many |
| R3-206232 | Draft LS on Test Procedures for PWS | Ericsson, One2many |
| R3-206233 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-206234 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-206235 | Correction of SNPN failures | Nokia, Nokia Shanghai Bell, Orange |
| R3-206236 | Max number of F1-C links is exceeded at CU | Ericsson, Verizon Wireless, CMCC |
| R3-206237 | Max number of F1-C links is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless, CMCC |
| R3-206239 | Max number of F1-C links is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless, CMCC |
| R3-206242 | MRO Inter-system measurement Configuration | Ericsson |
| R3-206243 | MRO S1AP clarifications for Inter-system measurement Configuration | Ericsson |
| R3-206246 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson, AT&T, Verizon Wireless |
| R3-206249 | Addition of Local NG-RAN Node Identifier. | Ericsson, AT&T, Verizon Wireless |
| R3-206283 | Add the support for updating RG Level Wireline Access Characteristics and Global Cable ID | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel, Charter Communications |
| R3-206284 | Add the support for updating RG Level Wireline Access Characteristics | Nokia, Nokia Shanghai Bell, Huawei, BT, Intel, Charter Communications |
| R3-206285 | Clarification for F1-C Traffic Container IE | Nokia, Nokia Shanghai Bell, Huawei, Samsung, Qualcomm |
| R3-206286 | Uniqueness of BH RLC channel ID | Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE |
| R3-206293 | Correction on Abnormal Conditions in Handover Preparation Procedure (R15) | CATT |
| R3-206334 | CR38413 for clarification on UE-associated signalling for NBIOT procedures in Rel-16 | ZTE, Ericsson, Qualcomm Incorporated |
| R3-206335 | CR38413 for clarification on UE-associated signalling in Rel-15 | ZTE, Ericsson |
| R3-206336 | CR38413 for clarification on UE-associated signalling in Rel-16 | ZTE, Ericsson |
| R3-206351 | Correction CR on Network instance for 38.413(R15) | CATT |
| R3-206352 | Correction CR on Network instance for 38.423(R15) | CATT |
| R3-206353 | Issue of intra gNB-CU-UP DAPS HO | CATT |
| R3-206354 | CR to TS 38463 for Intra gNB-CU-UP DAPS HO | CATT |
| R3-206366 | Clarification on an abnormal condition in PDU Session Resource Modify Procedure | ZTE, China Telecom, CMCC |
| R3-206367 | Clarification on an abnormal condition in PDU Session Resource Modify Procedure | ZTE, China Telecom, CMCC |
| R3-206407 | MeNB involvement in SCG release for UE power saving | Huawei |
| R3-206451 | Correction of ARP | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-206452 | Correction of ARP | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-206453 | Correction on Expected UE activity behaviour | Lenovo, Motorola Mobility, Huawei, Samsung |
| R3-206461 | Introducing AQP in path switch request acknowledge message | Huawei, Orange, BT, Vodafone |
| R3-206462 | Correction of alternative QoS profile | Huawei, Orange, Vodafone |
| R3-206463 | Correction of alternative QoS profile | Huawei, Orange, Vodafone |
| R3-206464 | Corrections of MLB | Huawei |
| R3-206465 | Corrections of MLB and MDT | Huawei |
| R3-206466 | Corrections of MLB | Huawei |
| R3-206467 | Removal of duplicated imports | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-206468 | Corrections of UL and DL carrier list | Huawei |
| R3-206469 | Introducing UE radio capability ID in Connection Establishment Indication | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-206470 | Introducing UE radio capability ID in Connection Establishment Indication | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-206471 | Notification of RACS feature not supported | Huawei, Samsung, CATT |
| R3-206472 | Notification of RACS feature not supported | Huawei, Samsung, CATT |
| R3-206473 | Notification of RACS feature not supported | Huawei, Samsung, CATT |
| R3-206474 | Notification of RACS feature not supported | Huawei, Samsung, CATT |
| R3-206475 | Correction on Expected UE activity behaviour | Huawei, Lenovo, Motorola Mobility |
| R3-206476 | Addition of parameters to Alternative QoS: MDBV | Huawei, Orange, Vodafone |
| R3-206477 | Addition of parameters to Alternative QoS: MDBV | Huawei, Orange, Vodafone |
| R3-206478 | Addition of parameters to Alternative QoS: MDBV | Huawei, Orange, Vodafone |
| R3-206481 | Addition of parameters to Alternative QoS: MDBV | Huawei, Orange, Vodafone |
| R3-206482 | Correction on Expected UE activity behaviour | Huawei, Lenovo, Motorola Mobility |
| R3-206494 | Correction Ethernet Compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-206495 | LS on Synchronization of Ethernet compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-206496 | Correction of RAN CP Relocation | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| R3-206504 | Corrections on AQP for notification control | Ericsson, Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics, Intel Corporation |
| R3-206551 | NGAP correction on Global eNB ID in Target ID IE | Ericsson, ZTE, NEC, CATT, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-206557 | Correction of NRPPa positioning procedures | Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-206584 | Correction of NRPPa periodic UL SRS time transmission | Ericsson, ZTE |
| R3-206585 | Correction of F1AP periodic UL SRS time transmission | Ericsson, ZTE |
| R3-206591 | Including SRS frequency information Postioning Information Request | Huawei |
| R3-206592 | Including SRS frequency informationing Postioning Information Request | Huawei |
| R3-206593 | RRC alignement and various correction including ASN.1 | Huawei |
| R3-206594 | RRC alignement and various correction including ASN.1 | Huawei |
| R3-206595 | Including Cell ID in the measurement request | Huawei |
| R3-206613 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-206614 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-206615 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-206617 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-206618 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-206621 | UL primary path signaling over E1 | Ericsson |
| R3-206622 | UL primary path signaling over E1 | Ericsson |
| R3-206630 | Direct forwarding path availability in Handover Required message | Huawei |
| R3-206631 | Direct forwarding path availability in Handover Required message | Huawei |
| R3-206632 | Support of shared-DU and dedicated logical-CU for NPN | Huawei, China Telecom |
| R3-206633 | Introducing the secondary NG-RAN node ID in PDU Session Resource Modify Response message | Huawei, CATT, ZTE, Intel Corporation |
| R3-206634 | Clarification of Mobility Restriction List | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-206635 | Clarification of Mobility Restriction List | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-206636 | Introducing Additional Duplication Activation over E1 | Huawei, CATT, CMCC |
| R3-206637 | Discussion on the size limitation of DTLS over SCTP | Huawei, China Telecom |
| R3-206638 | Correction of Allocated C-RNTI for 2-step RACH | Huawei, CMCC |
| R3-206639 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei |
| R3-206640 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei |
| R3-206641 | Correction of RLC Duplication Information over F1 | Huawei, Intel Corporation, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-206642 | UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-206643 | Discussion on Maximum Number of Cells per gNB | Nokia, Nokia Shanghai Bell |
| R3-206644 | Max number of cells per NG-RAN Node | Nokia, Nokia Shanghai Bell |
| R3-206645 | Discussion on NSA-SA Cell Operation | Nokia, Nokia Shanghai Bell |
| R3-206646 | NSA-SA Cell Operation | Nokia, Nokia Shanghai Bell |
| R3-206651 | PLMN Not Supported Cause Value | Nokia, Nokia Shanghai Bell |
| R3-206659 | Correction on unsuccessful operations of IAB procedures | Huawei |
| R3-206660 | Correction on the identification of IAB-donor-DU | Huawei, Lenovo, Motorola Mobility, CATT, Samsung |
| R3-206661 | Correction on the Context Setup procedure for IAB node | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-206662 | Correction on BAP address | Huawei, Nokia, Nokia Shanghai Bell, Samsung, Lenovo, Motorola Mobility |
| R3-206682 | CR for TS38.401 on Signalling based MDT Activation | ZTE, China Telecom |
| R3-206684 | Correction on Abnormal Conditions in Handover Preparation Procedure (R16) | CATT |
| R3-206705 | NGAP cause value for UE context transfer_R15 | ZTE,China Telecom |
| R3-206706 | NGAP cause value for UE context transfer_R16 | ZTE,China Telecom |
| R3-206707 | XnAP cause value for UE context transfer_R15 | ZTE,China Telecom |
| R3-206708 | XnAP cause value for UE context transfer_R16 | ZTE,China Telecom |
| R3-206709 | Correction on MDT location information on NGAP | ZTE,China Telecom |
| R3-206710 | Correction on MDT location information on F1AP | ZTE,China Telecom |
| R3-206711 | Correction on value range of UAC reduction Indication | ZTE, Nokia, Nokia, Nokia Shanghai Bell ,China Telecom |
| R3-206712 | Correction on value range of UAC reduction Indication_R16 | ZTE, Nokia, Nokia, Nokia Shanghai Bell ,China Telecom |
| R3-206719 | Introducing the secondary NG-RAN node ID in PDU Session Resource Modify Response message | Huawei, CATT, ZTE, Intel Corporation |
| R3-206724 | Discussion on Enhancement of MLB in R-16 | ZTE, China Telecom |
| R3-206725 | CR for TS38.423 on Enhancement of MLB in R-16 | ZTE, China Telecom |
| R3-206726 | CR for TS38.473 on Enhancement of MLB in R-16 | ZTE, China Telecom |
| R3-206727 | Discussion on Left Issues of MLB in R-16 | ZTE, China Telecom |
| R3-206728 | CR for TS38.423 on Left Issues of MLB in R-16 | ZTE, China Telecom |
| R3-206736 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-206737 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-206738 | Correction on Industrial IOT Rel-16 PDCP duplication for E1AP | Intel Corporation, ZTE, Huawei, CATT, Ericsson |
| R3-206739 | X2AP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-206740 | XnAP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-206745 | Correction on the semantics description of the PDCP SN Status Information IE in the DRB Modified List | Samsung |
| R3-206746 | Discussion on RAN Sharing Enhancement for MLB | ZTE, China Telecom |
| R3-206749 | Correction of the DAPS Response Information IE in the tabular | Samsung |
| R3-206750 | CR for TS38.300 on RAN Sharing Enhancement for MLB | ZTE, China Telecom |
| R3-206751 | Clarifiation on the DAPS HO response per E-RABs | Samsung |
| R3-206752 | Clarifiation on the DAPS HO response per DRBs | Samsung |
| R3-206753 | CR for TS38.423 on RAN Sharing Enhancement for MLB | ZTE, China Telecom |
| R3-206757 | Discussion and solution on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-206758 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-206759 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-206760 | Measurement gap deactivation over F1AP | Ericsson, Verizon Wireless |
| R3-206761 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Verizon Wireless |
| R3-206762 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Verizon Wireless |
| R3-206763 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206764 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206765 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206766 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206767 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206768 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206769 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-206770 | How to release NR-NR DC configurations between MN-CU and MN-DU | Ericsson, Verizon Wireless |
| R3-206771 | How to release NR-NR DC configurations between MN-CU and MN-DU | Ericsson, Verizon Wireless |
| R3-206772 | How to release NR-NR DC configurations between MN-CU and MN-DU | Ericsson, Verizon Wireless |
| R3-206773 | MeasGapConfig IE and the Configuration Query IE | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-206774 | MeasGapConfig IE and the Configuration Query IE CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-206775 | MeasGapConfig IE and the Configuration Query IE CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-206777 | Rapporteur Corrections to 38.425 | Samsung |
| R3-206805 | Misalignment between tabular and ASN.1 | Samsung |
| R3-206808 | Transparent signalling of MeasGapConfig IE at gNB-CU | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-206809 | Transparent signalling of MeasGapConfig IE at gNB-CU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-206810 | Transparent signalling of MeasGapConfig IE at gNB-CU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom |
| R3-206811 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless, CMCC |
| R3-206812 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless, CMCC |
| R3-206813 | Node Identifier for RRC Inactive | Ericsson, AT&T, Verizon Wireless |
| R3-206814 | Handling of unknown RRC establishment cause | Ericsson, China Telecom, China Unicom |
| R3-206815 | Handling of unknown RRC establishment cause | Ericsson, China Telecom, China Unicom |
| R3-206816 | Handling of unknown RRC establishment cause | Ericsson, China Telecom, China Unicom |
| R3-206817 | Correction on XnAP ASN.1 | Ericsson |
| R3-206818 | LS on NSSAI signalling in RRC Setup Complete | Ericsson |
| R3-206819 | Correction on NSSAI signalling in RRC Setup Complete, CR to 38.300 | Ericsson |
| R3-206821 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson, AT&T, Verizon Wireless, Vodafone |
| R3-206826 | CR for TS38.423 on primary LCID | ZTE |
| R3-206827 | Addition of Local NG-RAN Node Identifier. | Ericsson, AT&T, Verizon Wireless, Vodafone |
| R3-206905 | Response to R3-206813, R3-206821 and R3-206827 | Nokia, Nokia Shanghai Bell |
| R3-206916 | CB: # 67_IAB_Rel-16_Corrections - Summary of email discussion | Qualcomm - moderator |
| R3-206917 | CB: # 68_Positioning_Rel-16_Corrections - Summary of email discussion | Huawei - moderator |
| R3-206918 | CB: # 69_Rel-16_AQP_MDBV - Summary of email discussion | Ericsson - moderator |
| R3-206922 | Corrections of UL and DL carrier list | Huawei, China Telecom, Samsung |
| R3-206939 | Correction on DSCP Derivation in IAB-donor node | Perspecta Labs Inc., CISA ECD, AT&T |
| R3-206940 | CR38413 for clarification on UE-associated signalling in Rel-15 | ZTE, Ericsson |
| R3-206941 | Corrections of MLB | Huawei |
| R3-206942 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-206943 | Corrections on PCI Reconfiguration | Ericsson, Verizon Wireless |
| R3-206955 | Corrections of MLB and MDT | Huawei |
| R3-206956 | Corrections of UL and DL carrier list | Huawei, China Telecom, Samsung |
| R3-206957 | NGAP correction on Global eNB ID in Target ID IE | Ericsson, ZTE, NEC, CATT, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-206958 | CB: # 87_IntraSysHOdatafwd_fullConfig - Summary of email discussion | Samsung - moderator |
| R3-206959 | Correction of RLC Duplication Information over F1 | Huawei, Intel Corporation, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-206960 | CB: # 88_E1SetupVirtualizedCU-UPs - Summary of email discussion | Ericsson - moderator |
| R3-206961 | CR to TS36.423 on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE,CATT |
| R3-206962 | CB: # 89_LTE-NRrelTimingIndication - Summary of email discussion | China Telecom - moderator |
| R3-206963 | CB: # 90_CPCcompleteTrsf - Summary of email discussion | Google - moderator |
| R3-206964 | CB: # 92_ExpectedUEActBehavior - Summary of email discussion | Huawei - moderator |
| R3-206965 | CB: # 91_LosslessIntraSysHO - Summary of email discussion | Samsung - moderator |
| R3-206966 | CB: # 93_UEradioCapIDconnEstInd - Summary of email discussion | Huawei - moderator |
| R3-206967 | CB: # 94_LocalNodeID - Summary of email discussion | Ericsson - moderator |
| R3-206968 | CB: # 95_InsuffUEcapCauseValue - Summary of email discussion | Ericsson - moderator |
| R3-206969 | CB: # 96_SecondaryNG-RANnodeID - Summary of email discussion | Huawei - moderator |
| R3-206973 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-206974 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-206975 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson, AT&T, Verizon Wireless, Vodafone |
| R3-206976 | Correction on CPC Complete Transfer | Google Inc., NEC, Samsung, CATT |
| R3-206977 | Correction on CPC Complete Transfer | Google Inc., NEC, Samsung, CATT |
| R3-206978 | Correction on CPC Complete Transfer | Google Inc., NEC, Samsung, CATT |
| R3-206981 | Introducing AQP in path switch request acknowledge message | Huawei, Orange, BT, Vodafone |
| R3-206982 | Correction of alternative QoS profile | Huawei, Orange, Vodafone |
| R3-206983 | Correction of alternative QoS profile | Huawei, Orange, Vodafone |
| R3-206985 | CB: # 97_maxF1-Clinks - Summary of email discussion | Ericsson - moderator |
| R3-206986 | CR38413 for clarification on UE-associated signalling for NBIOT procedures in Rel-16 | ZTE, Ericsson, Qualcomm Incorporated |
| R3-206987 | CR38413 for clarification on UE-associated signalling in Rel-16 | ZTE, Ericsson |
| R3-206988 | CB: # 98_MeasGapConfig - Summary of email discussion | Ericsson - moderator |
| R3-206989 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless, CMCC |
| R3-206990 | CB: # 99_RRCre-est - Summary of email discussion | Ericsson - moderator |
| R3-206991 | CB: # 100_UnknownRRCest_cause - Summary of email discussion | Ericsson - moderator |
| R3-206992 | CB: # 101_SCGrelease_UEpwrSaving - Summary of email discussion | ZTE - moderator |
| R3-206993 | CB: # 102_AbnormalCondPDUSessResMod - Summary of email discussion | ZTE - moderator |
| R3-206994 | Correction on value range of UAC reduction Indication | ZTE, Nokia, Nokia, Nokia Shanghai Bell ,China Telecom, Ericsson |
| R3-206995 | Correction on value range of UAC reduction Indication | ZTE, Nokia, Nokia, Nokia Shanghai Bell ,China Telecom, Ericsson |
| R3-206996 | Correction on V2X related information | Google Inc., Ericsson |
| R3-206997 | CB: # 104_MobRestr_Snadd - Summary of email discussion | Nokia - moderator |
| R3-206998 | (reserved) | nn |
| R3-206999 | CB: # 105_FlexNodeLength - Summary of email discussion | Ericsson - moderator |
| R3-207000 | LS on broadcasting gNB ID length in system information block | Ericsson, Verizon Wireless |
| R3-207001 | Correction of UE Release Request | Nokia, Nokia Shanghai Bell, Orange |
| R3-207002 | draftLS to SA2 | Nokia |
| R3-207005 | CB: # 106_UEreleaseReq - Summary of email discussion | Nokia - moderator |
| R3-207017 | RRC alignement and various correction including ASN.1 | Huawei |
| R3-207018 | RRC alignement and various correction including ASN.1 | Huawei |
| R3-207019 | Including SRS frequency information Postioning Information Request | Huawei |
| R3-207020 | Including SRS frequency informationing Postioning Information Request | Huawei |
| R3-207021 | Coupling TRP ID and Cell ID in Measurement procedures | Huawei |
| R3-207043 | Corrections on AQP for notification control | Ericsson, Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics, Intel Corporation |
| R3-207065 | Correction of Intra-system HO for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility, Google Inc., CATT, Nokia, Nokia Shanghai Bell |
| R3-207066 | Correction of Intra-system HO data forwarding for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility, Google Inc., CATT, Nokia, Nokia Shanghai Bell |
| R3-207068 | Clarification for F1-C Traffic Container IE | Nokia, Nokia Shanghai Bell, Huawei, Samsung, Qualcomm |
| R3-207069 | Uniqueness of BH RLC channel ID | Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE |
| R3-207070 | CR on F1-C transfer for Rel-16 IAB | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
| R3-207078 | Correction on unsuccessful operations of IAB procedures | Huawei |
| R3-207079 | Correction on the Context Setup procedure for IAB node | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-207103 | Introducing UE radio capability ID in Connection Establishment Indication | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-207104 | Introducing UE radio capability ID in Connection Establishment Indication | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-207105 | LS on PDU Session level "Expected UE activity behaviour" | Huawei |
| R3-207113 | Introduction of 5GC Mobility Restriction List Container IE in S-Node Addition | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm |
| R3-207115 | CR38423 for NR SCG release for power saving | ZTE, NEC, China Telecom |
| R3-207116 | Corrections on AQP for notification control | ZTE, Ericsson, Nokia,Nokia Shanghai Bell |
| R3-207126 | Clarification of 5GC Mobility Restriction List Container | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-207127 | Corrections to tabular and asn.1 for NR positioning (NRPPa) | Nokia, Nokia Shanghai Bell |
| R3-207128 | Corrections to tabular and asn.1 for NR positioning (F1AP) | Nokia, Nokia Shanghai Bell |
| R3-207129 | Coupling TRP ID and Cell ID in Measurement procedures | Huawei |
| R3-207130 | LS on Rel-16 NR Positioning Correction to RAN1 and RAN2 | Huawei |
| R3-207131 | Correction on DSCP Derivation in IAB-donor node | Perspecta Labs Inc., CISA ECD, AT&T |
| R3-207134 | Correction in F1-U on DSCP Derivation in IAB-donor node | Perspecta Labs Inc. |
| R3-207150 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-207151 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-207152 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-207153 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-207154 | Cause value on X2, Xn and F1 for insufficient UE capabilities and normal release | Ericsson, Verizon Wireless, Deutsche Telekom, CMCC |
| R3-207163 | Clarification on an abnormal condition in PDU Session Resource Modify Procedure | ZTE, China Telecom, CMCC |
| R3-207164 | Clarification on an abnormal condition in PDU Session Resource Modify Procedure | ZTE, China Telecom, CMCC |
| R3-207172 | Correction on V2X related information | Google Inc., Ericsson, ZTE |
| R3-207205 | CR to TS36.423 on the LTE-NR Relative Timing indication | China Telecom, Qualcomm Incorporated, ZTE,CATT |
| R3-207219 | Coupling TRP ID and Cell ID in Measurement procedures | Huawei |
| R3-207220 | LS on Rel-16 NR Positioning Correction to RAN1 and RAN2 | Huawei |
| R3-207221 | Correction of Intra-system HO for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility, Google Inc., CATT, Nokia, Nokia Shanghai Bell, Huawei |
| R3-207223 | LS on PDU Session level "Expected UE activity behaviour" | Huawei |
| R3-207226 | LS on broadcasting gNB ID length in system information block | Ericsson, Verizon Wireless |
| R3-207255 | Correction on value range of UAC reduction Indication | ZTE, Nokia, Nokia, Nokia Shanghai Bell ,China Telecom, Ericsson |
| R3-207256 | Correction on value range of UAC reduction Indication | ZTE, Nokia, Nokia, Nokia Shanghai Bell ,China Telecom, Ericsson |
| R3-207257 | Corrections to tabular and asn.1 for NR positioning (NRPPa) | Nokia, Nokia Shanghai Bell |
| R3-207258 | Coupling TRP ID and Cell ID in Measurement procedures | Huawei |
| R3-207259 | Correction of Intra-system HO for full configuration | Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility, Google Inc., CATT, Nokia, Nokia Shanghai Bell, Huawei |
| 9.3.7.2 | Pure Stage-2 Corrections | |
| R3-205944 | Correction on conditional reconfiguration for PSCell | Google Inc., Intel Corporation, CATT |
| R3-206013 | Issues in stage 2 on MRO | Samsung, CMCC |
| R3-206014 | Correction of MRO in stage 2 | Samsung, CMCC |
| R3-206066 | Support of RAN sharing for the disaggregated SNPN | China Telecommunication, Huawei, CATT |
| R3-206081 | Correction on NGAP functions | ZTE Corporation |
| R3-206082 | Correction on NGAP functions | ZTE Corporation |
| R3-206084 | Correction on NGAP functions | ZTE Corporation |
| R3-206085 | Correction on NGAP functions | ZTE Corporation |
| R3-206565 | CR to 38.470 on the introduction of IAB function and procedures | ZTE, Sanechips |
| R3-206596 | Dynamic UMTS Radio Capability impact on SRVCC and RACS | Huawei, HiSilicon, Vodafone |
| R3-206663 | Correction on clarification of non-F1 traffic | Huawei, CATT, Samsung, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-206664 | Correction on IAB procedures | Huawei |
| R3-206741 | Correction for LTE CHO and Full Configuration | Intel Corporation, Samsung |
| R3-206742 | Correction for NR CHO and Full Configuration | Intel Corporation, Samsung |
| R3-206743 | Correction for RRC Reconfiguration Complete Indicator for the first reconfiguration after RRC re-establishment via the last serving gNB-DU | Intel Corporation |
| R3-206744 | Correction for RRC Reconfiguration Complete Indicator for the first reconfiguration after RRC re-establishment via the last serving gNB-DU | Intel Corporation |
| R3-206820 | CHO in stage-2 | Ericsson |
| R3-206822 | Correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-206823 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-206824 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-206825 | CR for TS38.300 on PDCP duplication | ZTE |
| R3-206980 | CR to 38.470 on the introduction of IAB function and procedures | ZTE, Sanechips |
| 10.1 | General | |
| R3-205906 | MDT in MR-DC | Huawei |
| R3-205908 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-206779 | BLCR to 38.300: addition of SON features enhancement | CMCC |
| R3-206781 | Updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-206876 | CB: # 1000_SONMDT_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-207237 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-207238 | BLCR to 36.300_Addition of SON features enhancement | Lenovo |
| R3-207239 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-207240 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-207241 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-207242 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-207243 | MDT in MR-DC | Huawei |
| R3-207244 | BLCR to 36.401: Support of MDT enhancement | CMCC |
| R3-207245 | BLCR to 36.401: Support of MDT enhancement | CMCC |
| R3-207247 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm |
| R3-207252 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-207254 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility |
| 10.2.1.1 | PCI Selection | |
| R3-206096 | (TP for SON BL CR for TS 38.401): PCI selection in split architecture | Huawei |
| R3-206097 | (TP for SON BL CR for TS 38.473): PCI selection in split architecture | Huawei |
| R3-206156 | PCI Selection consideration | NEC |
| R3-206371 | Open points on PCI conflict detection and reassignment | Nokia, Nokia Shanghai Bell |
| R3-206506 | Discussion and Solution for Distributed PCI Selection | Ericsson, Verizon Wireless |
| R3-206652 | Further Discussion on PCI Selection in NR | ZTE |
| R3-206655 | TP for BL CR 38.300 on PCI Selection | ZTE |
| R3-206877 | CB: # 1001_SONMDT_PCISelect - Summary of email discussion | Huawei - moderator |
| R3-206979 | LS on PCI conflict detection and reassignment | Huawei |
| R3-207024 | CB: # 1001_SONMDT_PCISelect - Summary of email discussion | Huawei - moderator |
| R3-207157 | (TP for SON BL CR for TS 38.401): PCI selection in split architecture | Huawei |
| R3-207162 | TP for BL CR 38.300 on PCI Selection | ZTE |
| R3-207210 | (TP for SON BL CR for TS 38.401): PCI selection in split architecture | Huawei |
| R3-207212 | (TP for SON BL CR for TS 38.401): PCI selection in split architecture | Huawei |
| 10.2.1.2 | Energy Efficiency | |
| R3-206507 | Way forward on Energy Efficiency | Ericsson |
| R3-206692 | Further Discussion on RAN energy efficiency | ZTE, China Unicom ,China Telecom |
| R3-206693 | (TP for SON BL CR for TS 38.300) RAN energy efficiency | ZTE, China Unicom ,China Telecom |
| R3-206878 | CB: # 1002_SONMDT_EnergyEff - Summary of email discussion | Ericsson - moderator |
| R3-207014 | Reply LS on on energy efficiency | Ericsson |
| R3-207025 | CB: # 1002_SONMDT_EnergyEff - Summary of email discussion | Ericsson - moderator |
| 10.2.1.3 | Successful Handover Report | |
| R3-206048 | TP for SON BLCR for 38.423: Successful Handover Report | Samsung |
| R3-206049 | TP for SON BLCR for 38.413: Successful Handover Report | Samsung |
| R3-206050 | TP for SON BLCR for 38.473: Successful Handover Report | Samsung |
| R3-206063 | Discussion on support of Successful Handover report | China Telecommunications |
| R3-206080 | (TP for 38.423) Introducing the successful HO report in XnAP | China Telecommunications |
| R3-206083 | (TP for 38.473) Introducing the successful HO report in F1AP | China Telecommunications |
| R3-206144 | Discussion on successful handover report | CATT |
| R3-206324 | Discussion on successful handover report | CATT |
| R3-206508 | (TP for SON BL CR for TS 38.423/38.473): Successful Handover Report | Ericsson |
| R3-206509 | (TP for SON BL CR for TS 38.413): Inter RAT Energy Saving and Successful Handover support | Ericsson |
| R3-206879 | CB: # 1003_SONMDT_SuccessHO - Summary of email discussion | Samsung - moderator |
| R3-207012 | TP for SON BLCR for 38.423: Successful Handover Report | Samsung |
| R3-207026 | CB: # 1003_SONMDT_SuccessHO - Summary of email discussion | Samsung - moderator |
| R3-207166 | (TP for 38.473) Introducing the successful HO report in F1AP | China Telecommunications |
| R3-207181 | (TP for SON BL CR for TS 38.413): Inter RAT Energy Saving and Successful Handover support | Ericsson |
| R3-207208 | (TP for SON BLCR 38.473) Introducing the successful HO report in F1AP | China Telecommunications |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-206051 | TP for SON BLCR for 38.423: UE History Information in EN-DC | Samsung |
| R3-206052 | TP for SON BLCR for 36.423: UE History Information in EN-DC | Samsung |
| R3-206145 | Enhancement of UE history information in MR-DC scenario | CATT |
| R3-206146 | (TP on UE history information for 36.413) Addition of UE history information for SN | CATT |
| R3-206147 | (TP on UE history information for 36.423) Addition of UE history information for SN | CATT |
| R3-206148 | Draft LS to RAN2 on UE History Information in MR-DC | CATT |
| R3-206157 | UE History Information (UHI) in MR-DC | NEC |
| R3-206186 | UE History Information in MR-DC | Qualcomm Incorporated |
| R3-206188 | (TP for SON BLCR for 38.423) UE History Information in MR-DC | Huawei |
| R3-206189 | (TP for SON BLCR for 38.413) UE History Information in MR-DC | Huawei |
| R3-206325 | Enhancement of UE history information in MR-DC scenario | CATT |
| R3-206326 | (TP on UE history information for 36.413) Addition of UE history information for SN | CATT |
| R3-206327 | (TP on UE history information for 36.423) Addition of UE history information for SN | CATT |
| R3-206328 | Draft LS to RAN2 on UE History Information in MR-DC | CATT |
| R3-206510 | (TP for SON BL CR for TS 36.413/38.413/36.423): UE History Information for Secondary Node | Ericsson |
| R3-206748 | Discussion on collection of UE history information in EN-DC | NTT DOCOMO, INC. |
| R3-206829 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-206830 | (TP for SON BL CR for TS 37.340) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-206831 | (TP for SON BL CR for TS 36.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-206832 | (TP for SON BL CR for TS 38.413) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-206833 | (TP for SON BL CR for TS 38.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-206880 | CB: # 1004_SONMDT_UEHist - Summary of email discussion | Qualcomm - moderator |
| R3-206935 | (TP for SON BL CR for TS 36.413/38.413/36.423): UE History Information for Secondary Node | Ericsson |
| R3-207027 | CB: # 1004_SONMDT_UEHist - Summary of email discussion | Qualcomm - moderator |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-205952 | Load information enhancements | Nokia, Nokia Shanghai Bell |
| R3-205953 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Further clarification of the TNL load | Nokia, Nokia Shanghai Bell |
| R3-205954 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Further clarification of the TNL load | Nokia, Nokia Shanghai Bell |
| R3-205955 | (TP to TS 38.473, NR_ENDC_SON_MDT_enh-Core) Adding slice to the load information | Nokia, Nokia Shanghai Bell |
| R3-205956 | (TP to TS 38.463, NR_ENDC_SON_MDT_enh-Core) Adding slice to the load information | Nokia, Nokia Shanghai Bell |
| R3-205957 | A new overload mechanism for CU-DU split deployment | Nokia, Nokia Shanghai Bell |
| R3-205958 | (TP to TS 38.473, NR_ENDC_SON_MDT_enh-Core) RRC connection reject template | Nokia, Nokia Shanghai Bell |
| R3-205959 | Completion of the load information signalling in EN-DC | Nokia, Nokia Shanghai Bell, BT, Qualcomm Incorporated |
| R3-205960 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Completion of the load information signalling in EN-DC | Nokia, Nokia Shanghai Bell, BT, Qualcomm Incorporated |
| R3-206053 | TP for SON BLCR for 38.423: Load Balancing Enhancements | Samsung |
| R3-206133 | Discussion on PSCell MLB | CATT |
| R3-206187 | Enhancements to Mobility Settings Change Procedure | Qualcomm Incorporated |
| R3-206190 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei |
| R3-206313 | Discussion on PSCell MLB | CATT |
| R3-206511 | (TP for SON BL CR for TS 36.423, TS 38.423): MLB enhancements | Ericsson |
| R3-206648 | Open issue on load balancing enhancement | LG Electronics |
| R3-206656 | Further Discussion on Load Balancing Enhancements | ZTE |
| R3-206657 | TP for BL CR 38.423 on Load Balancing Enhancements | ZTE |
| R3-206658 | TP for BL CR 38.463 on Load Balancing Enhancements | ZTE |
| R3-206672 | TP for BL CR 38.473 on Load Balancing Enhancements | ZTE |
| R3-206789 | Load balancing enhancements | CMCC |
| R3-206881 | CB: # 1005_SONMDT_LoadBalancing - Summary of email discussion | Nokia - moderator |
| R3-207028 | CB: # 1005_SONMDT_LoadBalancing - Summary of email discussion | Nokia - moderator |
| R3-207110 | Completion of the load information signalling in EN-DC | Nokia, Nokia Shanghai Bell, British Telecommunications, Qualcomm Incorporated, ZTE, NEC |
| R3-207224 | Completion of the load information signalling in EN-DC | Nokia, Nokia Shanghai Bell, British Telecommunications, Qualcomm Incorporated, ZTE, NEC, Ericsson |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-205904 | Definitions for MRO scenarios for SN change failure | Nokia, Nokia Shanghai Bell |
| R3-205905 | Definitions of SCG failure events for MRO for SN change | Nokia, Nokia Shanghai Bell |
| R3-206017 | TP for SON BLCR for 38.423: Support of SN change failure | Samsung |
| R3-206018 | LS on information needed for MRO in SCG Failure Report | Samsung |
| R3-206064 | Support on MRO for SN Change Failure | China Telecommunications |
| R3-206141 | Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-206142 | (TP on SN Change failure for 38.423) Addition of SCG Failure Information transfer | CATT |
| R3-206143 | Draft LS to RAN2 on SN change failure | CATT |
| R3-206191 | (TP for SON BLCR for 38.423) MRO for SN Change Failure | Huawei |
| R3-206192 | (TP for SON BLCR for 37.340) MRO for SN Change Failure | Huawei |
| R3-206321 | Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-206322 | (TP on SN Change failure for 38.423) Addition of SCG Failure Information transfer | CATT |
| R3-206323 | Draft LS to RAN2 on SN change failure | CATT |
| R3-206512 | Issues related to SCGFailureInformation message delivery for MRO use case | Ericsson |
| R3-206694 | Further consideration on MRO SN change failure | ZTE |
| R3-206882 | CB: # 1006_SONMDT_SNChangeFail - Summary of email discussion | Samsung - moderator |
| R3-207029 | CB: # 1006_SONMDT_SNChangeFail - Summary of email discussion | Samsung - moderator |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-206104 | (TP for SON BL CR for TS 38.473): PRACH configuration conflict | Huawei |
| R3-206134 | Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-206135 | (TP on SON for 38.473)TP on PRACH coordination for F1AP | CATT |
| R3-206136 | (TP on SON for 38.423)TP on PRACH coordination for X2AP | CATT |
| R3-206314 | Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-206315 | (TP on SON for 38.473)TP on PRACH coordination for F1AP | CATT |
| R3-206316 | (TP on SON for 38.423)TP on PRACH coordination for X2AP | CATT |
| R3-206372 | RACH Remaining Aspects | Nokia, Nokia Shanghai Bell |
| R3-206373 | (TP for SON BL CR to TS 38.423) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-206374 | (TP for SON BL CR to TS 38.473) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-206513 | (TP for SON BL CR for TS38.473): RACH conflict resolution and RACH report | Ericsson |
| R3-206554 | Discussion on the PRACH Coordination between LTE and NR | China Telecom, ZTE, Huawei |
| R3-206555 | (TP for [NR_SON_MDT] BL CR for TS 38.423) Addition of LTE PRACH Coordination in XnAP | China Telecommunications |
| R3-206695 | Left issue for Rel-16 RACH Optimization | ZTE |
| R3-206883 | CB: # 1007_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| R3-207030 | CB: # 1007_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| R3-207171 | [DRAFT] LS on Applicability of E-UTRA / NR PRACH Coordination | Nokia, Nokia Shanghai Bell |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-206019 | TP for SON BLCR for 38.423: Support of CCO | Samsung |
| R3-206020 | TP for SON BLCR for 38.300: Support of CCO | Samsung |
| R3-206193 | (TP for SON BLCR for 38.423) Coverage and Capacity Optimization | Huawei |
| R3-206194 | (TP for SON BLCR for 38.473) Coverage and Capacity Optimization | Huawei |
| R3-206514 | (TP for SON BL CR for TS 38.423, TS 38.473, TS 36.423, TS 38.300): CCO | Ericsson |
| R3-206520 | (TP for SON BL CR for TS 36.423): CCO for EN-DC | Ericsson |
| R3-206674 | Further Discussion on Coverage and Capacity Optimization in NR | ZTE, CMCC, China Telecom |
| R3-206676 | TP for BL CR 38.300 on Coverage and Capacity Optimization | ZTE, CMCC, China Telecom |
| R3-206884 | CB: # 1008_SONMDT_CCO - Summary of email discussion | Huawei - moderator |
| R3-207031 | CB: # 1008_SONMDT_CCO - Summary of email discussion | Huawei - moderator |
| R3-207092 | (TP for SON BLCR for 38.423) Coverage and Capacity Optimization | Huawei |
| R3-207227 | (TP for SON BLCR for 38.423) Coverage and Capacity Optimization | Huawei |
| 10.2.3 | Inter-System Inter-RAT Energy Saving | |
| R3-206047 | TP for SON BLCR for 38.423: Inter-System Inter-RAT Energy Saving | Samsung |
| R3-206098 | (TP for SON BL CR for TS 38.413): Inter-system inter-RAT energy saving | Huawei |
| R3-206099 | (TP for SON BL CR for TS 36.413): Inter-system inter-RAT energy saving | Huawei |
| R3-206184 | Inter-System Energy Savings | Qualcomm Incorporated |
| R3-206515 | (TP for SON BL CR for TS 36.413): Inter-System Inter-RAT Energy Saving | Ericsson |
| R3-206536 | New Cell Status for Energy Saving Operation | China Telecommunications |
| R3-206696 | Consideration on inter-system inter-RAT energy saving | ZTE, China Telecom, China Unicom |
| R3-206697 | TP for Inter-System Inter-RAT Energy Saving to TS36.413 SON BLCR | ZTE, China Telecom, China Unicom |
| R3-206698 | (TP for SON BL CR for TS 36.413) Introduce Inter-System Inter-RAT Energy Saving | ZTE, China Telecom, China Unicom |
| R3-206699 | (TP for SON BL CR for TS 38.413) Introduce Inter-System Inter-RAT Energy Saving | ZTE, China Telecom, China Unicom |
| R3-206796 | Discussion on inter-system inter-RAT energy saving | CMCC |
| R3-206797 | TP to 36.300 for inter-system inter-RAT energy saving | CMCC |
| R3-206798 | TP to 36.413 for inter-system inter-RAT energy saving | CMCC |
| R3-206799 | TP to 38.300 for inter-system inter-RAT energy saving | CMCC |
| R3-206800 | TP to 38.413 for inter-system inter-RAT energy saving | CMCC |
| R3-206885 | CB: # 1009_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| R3-207007 | TP to 36.300 for inter-system inter-RAT energy saving | CMCC |
| R3-207008 | TP to 38.300 for inter-system inter-RAT energy saving | CMCC |
| R3-207032 | CB: # 1009_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| 10.2.4 | Inter-System Load Balancing | |
| R3-206185 | Inter-System Mobility Load Balancing | Qualcomm Incorporated |
| R3-206195 | (TP for SON BLCR for 38.413) Inter-System Load Balancing | Huawei |
| R3-206516 | (TP for SON for TS 38.300, TS 38.413, TS 36.300, TS 36.413): Inter-System Load Balancing BL CR | Ericsson |
| R3-206678 | Further Discussion on Inter-system Load Balancing in NR | ZTE |
| R3-206680 | TP for BL CR 38.300 on Inter-system Load Balancing | ZTE |
| R3-206681 | TP for BL CR 38.413 on Inter-system Load Balancing | ZTE |
| R3-206786 | Further discussion on inter-system load balancing | CMCC |
| R3-206793 | TP to 36.300 for inter-system load balancing | CMCC |
| R3-206794 | TP to 38.300 for inter-system load balancing | CMCC |
| R3-206886 | CB: # 1010_SONMDT_InterSystemLoad - Summary of email discussion | Ericsson - moderator |
| R3-206934 | (TP for SON for TS 38.300, TS 38.413, TS 36.300, TS 36.413): Inter-System Load Balancing BL CR | Ericsson |
| R3-207033 | CB: # 1010_SONMDT_InterSystemLoad - Summary of email discussion | Ericsson - moderator |
| 10.2.5 | Two-Step RACH Optimization | |
| R3-206105 | (TP for SON BL CR for TS 38.423): PRACH parameters coordination for 2-step RACH | Huawei |
| R3-206106 | (TP for SON BL CR for TS 38.473): PRACH parameters coordination for 2-step RACH | Huawei |
| R3-206137 | (TP on son for 38.473) TP for 2-step RACH | CATT |
| R3-206317 | TP for 2-step RACH | CATT |
| R3-206517 | 2-step RACH optimization for SON | Ericsson |
| R3-206887 | CB: # 1011_SONMDT_2StepRACH - Summary of email discussion | CATT - moderator |
| R3-207034 | CB: # 1011_SONMDT_2StepRACH - Summary of email discussion | CATT - moderator |
| R3-207158 | (TP on son for 38.473) TP for 2-step RACH | CATT |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-205950 | Data forwarding in case of a HO to wrong cell | Nokia, Nokia Shanghai Bell |
| R3-205951 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Data forwarding information in HO cancel procedure | Nokia, Nokia Shanghai Bell |
| R3-205998 | Discussion on SON enhancements for DAPS handover | Samsung |
| R3-206021 | Discussion on SON enhancements for CHO | Samsung |
| R3-206022 | TP for SON BLCR for 38.423: Support of MRO for CHO | Samsung |
| R3-206023 | LS on MRO for CHO and DAPS | Samsung |
| R3-206065 | Discussion on Mobility Enhancement Optimization | China Telecommunications |
| R3-206138 | Discussion on MRO for CHO mobility enhance | CATT |
| R3-206139 | Discussion on MRO for DAPS mobility enhance | CATT |
| R3-206158 | Mobility Enhancement Optimization: data forwarding on HO to wrong cell | NEC |
| R3-206196 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-206318 | Discussion on MRO for CHO mobility enhance | CATT |
| R3-206319 | Discussion on MRO for DAPS mobility enhance | CATT |
| R3-206454 | SON Enhancements for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-206455 | TP for SON BLCR for 38.300 - MRO for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-206456 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility, ZTE |
| R3-206457 | TP for SON BLCR for 38.300 - MRO for DAPS handover | Lenovo, Motorola Mobility, ZTE |
| R3-206518 | (TP for SON BL CR for TS 38.300): Mobility Robustness Optimization for Conditional Handover | Ericsson |
| R3-206519 | (TP for SON BL CR for TS 38.300): DAPS handover SON aspects | Ericsson |
| R3-206700 | MRO enhancements for CHO | ZTE |
| R3-206780 | Mobility optimization enhancement | CMCC |
| R3-206888 | CB: # 1012_SONMDT_MobEnh - Summary of email discussion | Lenovo - moderato |
| R3-206923 | TP for SON BLCR for 38.423: Support of MRO for CHO | Samsung |
| R3-207035 | CB: # 1012_SONMDT_MobEnh - Summary of email discussion | Lenovo - moderato |
| R3-207090 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-207132 | LS on Mobility Enhancement Optimization | lenovo |
| R3-207228 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-207229 | LS on Mobility Enhancement Optimization | lenovo |
| 10.3.2.1 | MDT Enhancements | |
| R3-205931 | Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO | SA WG5 |
| R3-205933 | Reply LS on the user consent for trace reporting | SA WG5 |
| R3-205934 | Reply LS on support for stream based MDT/Trace reporting | SA WG5 |
| R3-206100 | (TP for SON BLCR for TS 38.401): MDT coexistence with IDC | Huawei, LGU+ |
| R3-206101 | (TP for MDT BL CR for TS 38.473): MDT coexistence with IDC | Huawei, LGU+ |
| R3-206102 | (TP for MDT BL CR for TS 38.463): MDT coexistence with IDC | Huawei, LGU+ |
| R3-206103 | (TP for MDT BLCR for TS 38.401): User consent and data anonymization handling in split architecture in MR-DC | Huawei |
| R3-206428 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | Huawei |
| R3-206521 | (TP for SON BL CR for TS 38.413/38.423/36.413/36.423): Clarification for WLAN and Bluetooth measurements | Ericsson |
| R3-206522 | (TP for SON BL CR for TS 36.413/36.423): Enabling URI configuration within Trace Activation over S1AP and X2AP” | Ericsson |
| R3-206523 | (TP for SON BL CR for TS 38.423): Beam measurement inclusion in M1 measurement of immediate MDT | Ericsson |
| R3-206524 | (TP for SON BL CR for TS 38.413): Beam measurement inclusion in M1 measurement of immediate MDT over NGAP | Ericsson |
| R3-206542 | Reply LS on support for stream based MDT/Trace reporting | Ericsson |
| R3-206543 | Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO | Ericsson |
| R3-206544 | Reply LS on URI for streaming trace reporting in LTE | Ericsson |
| R3-206688 | MDT Enhancements coexistence with IDC for MDT in split architecture | ZTE |
| R3-206689 | (TP for SON BL CR for TS 38.401) Introduce Enhancements coexistence with IDC for MDT in split architecture | ZTE |
| R3-206690 | (TP for SON BL CR for TS 38.463) Introduce Enhancements coexistence with IDC for MDT in split architecture | ZTE |
| R3-206691 | (TP for SON BL CR for TS 38.473) Introduce Enhancements coexistence with IDC for MDT in split architecture | ZTE |
| R3-206889 | CB: # 1013_SONMDT_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-207015 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | Huawei, Ericsson |
| R3-207016 | (TP for MDT BLCR for TS 38.401): User consent and data anonymization handling in split architecture in MR-DC | Huawei |
| R3-207036 | CB: # 1013_SONMDT_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-207117 | (TP for SONMDT BLCR for 38.423) Propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE, Ericsson |
| R3-207202 | Enabling URI configuration within Trace Activation over S1 | Ericsson |
| R3-207203 | Enabling URI configuration within Trace Activation over X2 | Ericsson |
| R3-207204 | Reply LS on URI for streaming trace reporting in LTE | Ericsson |
| R3-207232 | Reply LS on URI for streaming trace reporting in LTE | Ericsson |
| 10.3.2.2 | MDT for MR-DC | |
| R3-206035 | TP for MDT BLCR for 38.473- MDT for MR-DC | Samsung |
| R3-206140 | (TP on MDT in MR-DC for 38.423) Addition of immediate MDT in NGEN-DC and NE-DC | CATT |
| R3-206149 | (TP on MDT enhancement for 36.423)Support of MDT enhancement for EN-DC | CATT |
| R3-206320 | (TP on MDT in MR-DC for 38.423) Addition of immediate MDT in NGEN-DC and NE-DC | CATT |
| R3-206329 | (TP on MDT enhancement for 36.423)Support of MDT enhancement for EN-DC | CATT |
| R3-206890 | CB: # 1014_SONMDT_MDTMR-DC - Summary of email discussion | CATT - moderator |
| R3-207037 | CB: # 1014_SONMDT_MDTMR-DC - Summary of email discussion | CATT - moderator |
| R3-207159 | (TP on MDT in MR-DC for 38.423) Addition of immediate MDT in NGEN-DC and NE-DC | CATT |
| R3-207169 | BLCR to 36.423:Support of MDT enhancement | CATT |
| 10.4 | Support for L2 Measurements | |
| R3-206525 | Clarification for delay measurements related to cases were CU-UP and DU are not split | Ericsson |
| R3-206891 | CB: # 1015_SONMDT_L2 - Summary of email discussion | Ericsson - moderator |
| R3-207038 | CB: # 1015_SONMDT_L2 - Summary of email discussion | Ericsson - moderator |
| R3-207155 | LS on corrections for F1-U delay reporting when gNB-DU and gNB-CU-UP are not split | Ericsson |
| R3-207233 | LS on corrections for F1-U delay reporting when gNB-DU and gNB-CU-UP are not split | Ericsson |
| 13.1 | General | |
| R3-206255 | Updated workplan for IAB enhancements | Qualcomm Incorporated (WI Rapporteur) |
| 13.2.1 | Inter-Donor IAB Node Migration | |
| R3-205981 | Considerations on UE migration procedure during Inter-donor IAB node migration | KDDI Corporation |
| R3-205999 | Discussion on inter-donor IAB node migration procedure | Samsung |
| R3-206107 | Discussion on inter-donor IAB migration | Fujitsu |
| R3-206208 | Inter-Donor IAB Node Migration Enhancement | Intel Deutschland GmbH |
| R3-206256 | Inter-donor IAB-node migration | Qualcomm Incorporated |
| R3-206287 | Discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-206292 | Discussion on Inter-donor migration | Google Inc. |
| R3-206294 | Inter IAB donor-CU topology adaptation | CATT |
| R3-206295 | Discussion on Simultaneous Connection to two IAB-donors | CATT |
| R3-206332 | Principles of Group Mobility for Inter-donor IAB-node Migration | AT&T |
| R3-206559 | Discussion on inter-Donor IAB Node Migration procedure | ZTE, Sanechips |
| R3-206560 | Consideration on supporting R16 CHO and DAPS in IAB | ZTE, Sanechips |
| R3-206586 | Inter-donor Load Balancing in IAB Networks | Ericsson |
| R3-206588 | On the Applicability of CHO for RLF Recovery in IAB Networks | Ericsson |
| R3-206665 | Inter-CU migration procedure | Huawei |
| R3-206666 | CHO and DAPS in R17 IAB | Huawei |
| R3-206854 | CB: # 11_IABinterDonorMigration - Summary of email discussion | Qualcomm - moderator |
| R3-206855 | CB: # 12_IABinterDonorMigration_CHOandDAPS - Summary of email discussion | Huawei - moderator |
| R3-207093 | CB: # 12_IABinterDonorMigration_CHOandDAPS - Summary of email discussion | Huawei - moderator |
| R3-207184 | LS on DAPS-like solution for service interruption reduction in Rel-17 IAB | Samsung |
| 13.2.2 | Reduction of Service Interruption | |
| R3-205961 | Considerations on IAB-donor indicator | KDDI Corporation |
| R3-206000 | Discussion on service interruption reduction for IAB | Samsung |
| R3-206001 | Discussion on mitigation on packet loss and unnecessary transmission | Samsung |
| R3-206209 | Mitigation of Packet Loss | Intel Deutschland GmbH |
| R3-206257 | Interruption time reduction for Intra-donor IAB-node migration | Qualcomm Incorporated |
| R3-206288 | discussion on Reduction of Service Interruption during Topology Adaptation | Nokia, Nokia Shanghai Bell |
| R3-206296 | Reducing the Service Interruption for IAB | CATT |
| R3-206558 | Discussion on inter-CU BH RLF recovery | ZTE, Sanechips |
| R3-206561 | Discussion on reduction of service interruption in intra-donor IAB node migration | ZTE, Sanechips |
| R3-206587 | On RLF Recovery Support for IAB Nodes | Ericsson |
| R3-206667 | Inter-CU RLF recovery procedure | Huawei |
| R3-206668 | Inter-CU BH RLF recovery procedure for IAB node | Huawei |
| R3-206856 | CB: # 13_IABreducingSvcInterruption - Summary of email discussion | Nokia - moderator |
| R3-207165 | CB: # 13_IABreducingSvcInterruption - Summary of email discussion | Nokia - moderator |
| 13.2.3 | Topology Redundancy | |
| R3-206002 | Discussion on inter-donor topology redundancy for IAB | Samsung |
| R3-206003 | Discussion on CP-UP separation for IAB | Samsung |
| R3-206072 | Open Issues on topological redundancy for IAB | LG Electronics |
| R3-206258 | IAB enhancements for inter-donor topological redundancy | Qualcomm Incorporated |
| R3-206289 | discussion on Inter-CU topology redundancy | Nokia, Nokia Shanghai Bell |
| R3-206290 | support F1-C Traffic Transfer over Xn interface | Nokia, Nokia Shanghai Bell |
| R3-206562 | Discussion on inter-donor redundancy | ZTE, Sanechips |
| R3-206669 | Discussion on IAB topological redundancy | Huawei |
| R3-206857 | CB: # 14_IABtopoRed - Summary of email discussion | Samsung - moderator |
| R3-207101 | CB: # 14_IABtopoRed - Summary of email discussion | Samsung - moderator |
| R3-207139 | LS on CP-UP separation for Rel-17 IAB | Samsung |
| R3-207167 | LS on inter-donor topology redundancy | Samsung |
| R3-207198 | LS on CP-UP separation for Rel-17 IAB | Samsung |
| R3-207199 | LS on inter-donor topology redundancy | Samsung |
| 13.3.1 | Congestion Mitigation | |
| R3-206004 | Discussion on UP-based congestion mitigation in IAB | Samsung |
| R3-206210 | Congestion Indication to CU-CP | Intel Deutschland GmbH |
| R3-206297 | Discuss the improvements to DDDS for IAB UP-based congestion mitigation | CATT |
| R3-206563 | Discussion on DL E2E flow and congestion control in R17-IAB | ZTE, Sanechips |
| R3-206589 | Downlink End-to-End Flow Control in IAB Networks | Ericsson |
| R3-206590 | CR TS 38.425 IAB End-to-End Flow Control Feedback | Ericsson |
| R3-206647 | Discussion on using DDDS for IAB congestion mitigation | Nokia, Nokia Shanghai Bell |
| R3-206649 | Discussion on CP-based approach for DL congestion mitigation | LG Electronics |
| R3-206671 | Discussion on IAB E2E flow control | Huawei |
| R3-206858 | CB: # 15_IABcongestionMitigation - Summary of email discussion | Ericsson - moderator |
| R3-207100 | CB: # 15_IABcongestionMitigation - Summary of email discussion | Ericsson - moderator |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-206298 | Consider on Multi-Hop Performance: QoS, Latency, Fairness | CATT |
| R3-206670 | Routing enhancement for IAB | Huawei |
| R3-206859 | CB: # 16_IABmultiHop - Summary of email discussion | CATT - moderator |
| R3-207168 | CB: # 16_IABmultiHop - Summary of email discussion | CATT - moderator |
| 13.4.2 | Others | |
| R3-206259 | Inter-donor coordination of IAB-DU resource management | Qualcomm Incorporated |
| R3-206564 | Discussion on IAB duplexing enhancements | ZTE, Sanechips |
| 14.2 | Signaling Support for Efficient Activation/Deactivation for One SCG and SCells | |
| R3-205963 | Inter-node signaling to support activation/deactivation of SCG | InterDigital |
| R3-205990 | Discussion on SCG deactivation and activation | ZTE |
| R3-205991 | Draft CR37340 for SCG deactivation and activation | ZTE |
| R3-206179 | Signaling for Efficient SCG activation/deactivation | Qualcomm Incorporated |
| R3-206337 | Consideration on Activation/Deactivation for One SCG and SCells | LG Electronics |
| R3-206341 | Discussion on support of efficient activation/de-activation mechanism for one SCG and Scells | Huawei |
| R3-206342 | Activation and de-activation of SCG | Huawei |
| R3-206343 | Activation and de-activation of SCG | Huawei |
| R3-206355 | Discussion on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-206356 | CR for TS 38.423 on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-206357 | CR for TS 38.473 on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-206480 | On support for SCG deactivation and activation | Lenovo, Motorola Mobility |
| R3-206497 | Support of SCG activation/de-activation mechanism | Ericsson |
| R3-206498 | Support of SCG activation/deactivation for MR-DC | Ericsson |
| R3-206499 | Support of SCG activation/deactivation for MR-DC | Ericsson |
| R3-206828 | Discussion on MN coordinated SGC (de-)activation | Samsung |
| R3-206892 | CB: # MRDC1-SCG_activation_deactivation - Summary of email discussion | ZTE - moderator |
| R3-207003 | CB: # MRDC1-SCG_activation_deactivation - Summary of email discussion | ZTE - moderator |
| 14.3 | Signaling Support for Conditional PSCell Change/Addition | |
| R3-205947 | Enhancements related to the conditional PSCell change | Nokia, Nokia Shanghai Bell |
| R3-205948 | Enabling inter-SN conditional PSCell change | Nokia, Nokia Shanghai Bell |
| R3-205949 | Enabling inter-SN conditional PSCell change | Nokia, Nokia Shanghai Bell |
| R3-205992 | Discussion on CPA and CPC | ZTE |
| R3-205993 | Draft CR37340 for support of CPAC | ZTE |
| R3-206062 | Discussion on Conditional PScell Mobility procedures | China Telecommunications |
| R3-206076 | CR on 38.423 for introducing CPC indicator in SN Addition procedure | China Telecommunications |
| R3-206079 | CR on 36.423 for introducing CPC indicator in SgNB Addition procedure | China Telecommunications |
| R3-206155 | CPA Signalling flow and discussion | NEC |
| R3-206178 | Conditional PSCell Addition and Change | Qualcomm Incorporated |
| R3-206282 | Consideration on support of conditional PScell Change/Addition | LG Electronics |
| R3-206344 | Discussion on Support of conditional PSCell change addition | Huawei |
| R3-206345 | Conditional PSCell change addition | Huawei |
| R3-206346 | Conditional PSCell change addition | Huawei |
| R3-206358 | Consideration on Scenarios for Conditional PSCell Change/Addition | CATT |
| R3-206359 | CR for 37.340 on Conditional PSCell Change/Addition | CATT |
| R3-206479 | On support of CPAC | Lenovo, Motorola Mobility |
| R3-206623 | Support of conditional PSCell change-addition | Ericsson |
| R3-206624 | Conditional SN Addition | Ericsson |
| R3-206625 | Conditional SN Addition | Ericsson |
| R3-206754 | Discussion on CPAC based on the conventional DC scenarios | Samsung |
| R3-206755 | Discussion on messages and IEs to support CPA | Samsung |
| R3-206756 | (TP for LTE_NR_DC_enh2-Core for TS 36.423) CPA related X2 messages | Samsung |
| R3-206893 | CB: # MRDC2-PSCell_Change_Addition - Summary of email discussion | Huawei - moderator |
| R3-207004 | CB: # MRDC2-PSCell_Change_Addition - Summary of email discussion | Huawei - moderator |
| 14.4 | Others | |
| R3-206626 | CHO in MR-DC operation | Ericsson |
| R3-206894 | CB: # MRDC3-Others - Summary of email discussion | Ericsson - moderator |
| 15.1 | General | |
| R3-206491 | time plan update for NR QoE SI | China Unicom |
| R3-206895 | CB: # NRQoE1-Timeplan - Summary of email discussion | China Unicom - moderator |
| R3-207097 | time plan update for NR QoE SI | China Unicom |
| R3-207120 | NR QoE progress in RAN3 | China Unicom, ZTE |
| R3-207234 | TR 38.890 v.0.2.0 | China Unicom |
| 15.2 | Triggering, Configuring, Measurement Collection and Reporting | |
| R3-206036 | Discussion on NR QoE solutions | Samsung |
| R3-206037 | pCR for TR 38.890 NR QoE solutions, procedures and interface impacts | Samsung |
| R3-206173 | QoE metrics correlation with radio | Qualcomm Incorporated |
| R3-206174 | QoE aware by gNB | Qualcomm Incorporated |
| R3-206175 | Interworking with LTE QoE | Qualcomm Incorporated |
| R3-206360 | Discussion on NR QoE solutions | CATT |
| R3-206361 | Discussion on RAN involved NR QoE | CATT |
| R3-206369 | Open points on QMC framework | Nokia, Nokia Shanghai Bell |
| R3-206370 | [Draft] LS on Framework for QoE Measurement Collection | Nokia, Nokia Shanghai Bell |
| R3-206397 | pCR for TR 38.890 Radio-related Measurements and Information in NR QoE Management | Ericsson |
| R3-206398 | pCR for TR 38.890 Mobility Support for NR QoE Management | Ericsson |
| R3-206399 | pCR for TR 38.890 Way Forward on Remaining Issues in NR QoE SI | Ericsson |
| R3-206492 | Further discussion on NR QoE solution | China Unicom |
| R3-206493 | Discussion on requirements and mechanisms for per slice QoE measurement | China Unicom, ZTE |
| R3-206535 | Further Consideration on QOE Configuration and Report | China Telecommunications |
| R3-206713 | Further Consideration On Study of NR QoE | ZTE |
| R3-206714 | TP for TR 38890 | ZTE |
| R3-206715 | Consideration on slice QoE measurement | ZTE |
| R3-206732 | Discussions on QoE report visibility at the RAN | Huawei |
| R3-206733 | Discussions on the radio related measurements and information as assistance to the NR QoE management functionality | Huawei, China Unicom, China Mobile |
| R3-206734 | Discussions on potential RAN3 impacts about the QoE measurement configuration, reporting and releasing under SA, NSA and MR-DC operation | Huawei, China Unicom |
| R3-206787 | Further discussion on NR QoE management | CMCC |
| R3-206795 | TP to 38.890 for NR QoE management | CMCC |
| R3-206834 | Discussion on signaling-based NR QoE management | LG Electronics |
| R3-206896 | CB: # NRQoE2-RANawareness - Summary of email discussion | Qualcomm - moderator |
| R3-206897 | CB: # NRQoE3-RANConfig_Report - Summary of email discussion | Huawei - moderator |
| R3-206898 | CB: # NRQoE4-Mobility - Summary of email discussion | Ericsson - moderator |
| R3-206899 | CB: # NRQoE5-Signalling_flow - Summary of email discussion | ZTE - moderator |
| R3-206900 | CB: # NRQoE6-Slice - Summary of email discussion | China Unicom - moderator |
| R3-207072 | Management-based signaling for NR QoE | ZTE |
| R3-207073 | Signaling-based signaling for NR QoE | Samsung |
| R3-207098 | TP for TR38.890 on per slice QoE measurement | China Unicom |
| R3-207112 | [Draft] LS on Framework for QoE Measurement Collection | Nokia, Nokia Shanghai Bell |
| R3-207118 | Discussions on the radio related measurements and information as assistance to the NR QoE management functionality | Huawei, China Unicom, China Mobile |
| R3-207119 | Discussions on potential RAN3 impacts about the QoE measurement configuration, reporting and releasing under SA, NSA and MR-DC operation | Huawei, China Unicom |
| R3-207141 | CB: # NRQoE2-RANawareness - Summary of email discussion | Qualcomm - moderator |
| R3-207142 | CB: # NRQoE3-RANConfig_Report - Summary of email discussion | Huawei - moderator |
| R3-207144 | pCR for TR 38.890 Mobility Support for NR QoE Management | Ericsson |
| R3-207145 | CB: # NRQoE4-Mobility - Summary of email discussion | Ericsson - moderator |
| R3-207185 | RAN visible QoE information reporting by UE | Qualcomm Incorporated, Samsung |
| R3-207186 | Discussions on the radio related measurements and information as assistance to the NR QoE management functionality | Huawei, China Unicom, China Mobile, Ericsson, Samsung, ZTE |
| R3-207187 | Discussions on potential RAN3 impacts about the QoE measurement configuration, reporting and releasing under SA, NSA and MR-DC operation | Huawei, China Unicom, Ericsson, Samsung, ZTE |
| R3-207189 | LS on Framework for QoE Measurement Collection | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-207190 | Management-based signaling for NR QoE | ZTE |
| R3-207191 | Signaling-based signaling for NR QoE | Samsung |
| R3-207192 | TP for TR38.890 on per slice QoE measurement | China Unicom, Samsung |
| R3-207201 | TP for TR38.890 Management based signalling for NR QoE | ZTE |
| R3-207213 | Signaling-based signaling for NR QoE | Samsung, ZTE, Ericsson |
| R3-207217 | pCR for TR 38.890 Mobility Support for NR QoE Management | Ericsson |
| R3-207225 | TP for TR38.890 Management based signalling for NR QoE | ZTE, Samsung, Ericsson |
| 17.1 | General | |
| R3-206567 | RAN impact of restricting the rate per UE per network slice | Nokia, Nokia Shanghai Bell |
| R3-206568 | Reply LS on restricting the rate per UE per network slice | Nokia, Nokia Shanghai Bell |
| R3-206735 | Draft TR 38.832 | CMCC, ZTE |
| R3-206792 | Updated work Plan for RAN Slicing | CMCC, ZTE |
| R3-206840 | LS on restricting the rate per UE per network slice | SA WG2 |
| R3-206841 | LS Reply on Enhancement of RAN Slicing | SA WG2 |
| R3-206867 | Reponse for R3-206840 | ZTE Corporation |
| R3-206868 | Reponse LS for R3-206840 | ZTE Corporation |
| R3-206901 | CB: # RANSlicing1-Workplan_TRSkeleton - Summary of email discussion | CMCC - moderator |
| R3-207041 | Reponse to restricting the rate per UE per network slice | ZTE |
| R3-207135 | Reponse to restricting the rate per UE per network slice | ZTE |
| R3-207206 | TR 38.832 0.3.0 | CMCC, ZTE |
| R3-207209 | comparison of solution 37 and 22 with and without DC | Nokia |
| R3-207230 | Reponse to restricting the rate per UE per network slice | ZTE |
| R3-207235 | TR 38.832 0.3.0 | CMCC, ZTE |
| 17.2 | Mechanisms to Support Service Continuity | |
| R3-206038 | Discussion on slice re-mapping scenarios | Samsung |
| R3-206039 | Discussion on slice remapping solutions | Samsung |
| R3-206040 | pCR for TR 38.832 evaluation of slice remapping scenarios and solutions | Samsung |
| R3-206238 | Solution for RAN congestion and Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-206240 | Remapping Solution involving 5GC for Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-206241 | Data forwarding Solution for Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-206260 | (TP for TR38.832) Additional slicing solutions | Qualcomm Incorporated |
| R3-206362 | Discussion on slice re-mapping principle | CATT |
| R3-206363 | Discussion on slice re-mapping due to slice resource shortage | CATT |
| R3-206364 | Discussion on slice re-mapping due to slice not supported | CATT |
| R3-206430 | Further discussion on the scenarios for network slice service continuity | Huawei, LGU+ |
| R3-206431 | Evaluation of slice re-mapping policy solutions | Huawei, LGU+ |
| R3-206432 | Solutions and Flow charts of network slice service continuity | Huawei, LGU+ |
| R3-206433 | Discussion on slice Re-mapping at mobility | Ericsson |
| R3-206434 | Text Proposal for slice Re-mapping at mobility | Ericsson |
| R3-206716 | Further Consideration On RAN slicing scenario | ZTE |
| R3-206717 | Further Consideration On RAN slicing solution | ZTE |
| R3-206788 | Further discussion on service continuity for slicing | CMCC |
| R3-206806 | Further consideration on additional issues for slice remapping | LG Electronics |
| R3-206807 | (TP for 38.832) Additional issues for slice remapping | LG Electronics |
| R3-206902 | CB: # RANSlicing2-Slice_Solutions_and_Evaluation - Summary of email discussion | Nokia - moderator |
| R3-207082 | Solution for RAN congestion and Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-207083 | Remapping Solution involving 5GC for Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-207106 | Further discussion on the scenarios for network slice service continuity | Huawei, LGU+ |
| R3-207107 | Evaluation of slice re-mapping policy solutions | Huawei, LGU+ |
| R3-207108 | Solutions and Flow charts of network slice service continuity | Huawei, LGU+ |
| R3-207114 | Evaluation of the solutions for RAN slicing enhancement | Samsung |
| R3-207124 | (TP for TR38.832) Additional slicing solutions | Qualcomm Incorporated |
| R3-207133 | Response to LS Reply on enhancement of RAN slicing | CMCC, ZTE |
| R3-207136 | Solution for RAN congestion and Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-207143 | CB: # RANSlicing2-Slice_Solutions_and_Evaluation - Summary of email discussion | Nokia - moderator |
| R3-207146 | Remapping Solution involving 5GC for Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-207193 | Remapping Solution involving 5GC for Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-207194 | Solutions and Flow charts of network slice service continuity | Huawei, LGU+ |
| R3-207195 | Evaluation of the solutions for RAN slicing enhancement | Samsung |
| R3-207196 | Response to LS Reply on enhancement of RAN slicing | CMCC, ZTE |
| R3-207197 | Text Proposal for slice Re-mapping at mobility | Ericsson |
| R3-207231 | Response to LS Reply on enhancement of RAN slicing | CMCC, ZTE |
| R3-207236 | Response to LS Reply on enhancement of RAN slicing | CMCC, ZTE |
| 17.3 | Others | |
| R3-206435 | Analysis of KI#7 on Fast Access To Network Slices | Ericsson |
| R3-206903 | CB: # RANSlicing3-SA2impact - Summary of email discussion | Ericsson - moderator |
| R3-207216 | (reserved)Response to LS on 5GC assisted cell selection for accessing network | Ericsson |
| 18.1 | General | |
| R3-206368 | General introduction of AI | ZTE Corporation |
| R3-206402 | On table of contents for the TR on “further enhancement for data collection” study | Intel Corporation |
| R3-206683 | General introduction of AI | ZTE, China Unicom |
| R3-206778 | Skeleton for TR 37.817 v0.0.0 | CMCC |
| R3-206804 | Work plan for Study on enhancement for data collection for NR and EN-DC | CMCC |
| R3-206872 | CB: # 24_EnhDataColl_General - Summary of email discussion | CMCC - moderator |
| R3-207081 | Skeleton for TR 37.817 v0.0.0 | CMCC |
| R3-207094 | Skeleton for TR 37.817 v0.0.0 | CMCC |
| R3-207253 | TR 37.817 v0.1.0 | CMCC |
| 18.2 | High-Level Principles and Definitions | |
| R3-206041 | Discussion on High-Level Principles for RAN Intelligence | Samsung |
| R3-206091 | General Principles for AI study | ZTE Corporation, China Unicom |
| R3-206170 | AI/ML framework | Qualcomm Incorporated |
| R3-206197 | High-level principles and definitions for AI/ML in RAN | Deutsche Telekom AG |
| R3-206333 | High-Level Overview of Artificial Intelligence in RAN | AT&T |
| R3-206338 | Considerations on high-level principle and definition for AI support in NG-RAN | CATT |
| R3-206375 | (TP for TR 37.817) Terminology for functional framework for machine learning and RAN intelligence | Nokia, Nokia Shanghai Bell |
| R3-206403 | Use cases, AI/ML algorithms, and general concepts | Intel Corporation |
| R3-206438 | Definitions and Working Assumptions for the study on AI/ML for NG-RAN | Ericsson |
| R3-206729 | Initial discussions on further enhancement for data collection | Huawei |
| R3-206783 | High-level framework for AI enabled RAN optimisation | CMCC |
| R3-206873 | CB: # 25_EnhDataColl_Princ_Defs - Summary of email discussion | Samsung - moderator |
| R3-207095 | CB: # 25_EnhDataColl_Princ_Defs - Summary of email discussion | Samsung - moderator |
| R3-207096 | Discussion on High-Level Principles for RAN Intelligence | Samsung |
| R3-207218 | Discussion on High-Level Principles for RAN Intelligence | Samsung, Ericsson, Huawei |
| 18.3 | Use Cases for Artificial Intelligence in RAN and Potential Benefits | |
| R3-206042 | Discussion on Use Cases for Artificial Intelligence in RAN and Potential Benefits | Samsung |
| R3-206171 | AI/ML use cases | Qualcomm Incorporated |
| R3-206198 | Use cases for AI/ML in RAN and potential benefits | Deutsche Telekom AG |
| R3-206339 | Discussion on use cases for artificial Intelligence in RAN | CATT |
| R3-206376 | AI/ML Considerations and Examplary Use Cases | Nokia, Nokia Shanghai Bell |
| R3-206437 | AI/ML based Use Cases | Ericsson |
| R3-206718 | AI based UE Trajectory Prediction | ZTE, Lenovo, Motolora mobility, CMCC, China Unicom |
| R3-206720 | AI based Energy Saving | ZTE, Lenovo, Motolora mobility, China Unicom |
| R3-206721 | Machine Learning assisted Load Prediction | ZTE, Lenovo, Motolora mobility, China Unicom |
| R3-206730 | Initial discussions on Use Cases for Artificial Intelligence in RAN | Huawei |
| R3-206803 | Use Cases for Artificial Intelligence in RAN | CMCC |
| R3-206874 | CB: # 26_EnhDataColl_UseCases - Summary of email discussion | Huawei - moderator |
| 18.4 | Standards Impact on Existing Nodes, Functions, and Interfaces | |
| R3-206043 | Discussion on Standards Impact on Existing Nodes, Functions, and Interfaces | Samsung |
| R3-206092 | Initial Analyse on the Interface Impact with AI-based RAN Architecture | ZTE Corporation, China Unicom |
| R3-206172 | Standard impact analysis | Qualcomm Incorporated |
| R3-206340 | Standards impact for mobility and load forecast case | CATT |
| R3-206436 | Initial Analysis of Standardisation Impacts for AI/ML | Ericsson |
| R3-206731 | Initial discussions on AI/ML for data collection | Huawei |
| R3-206782 | Preliminary analysis of standard impacts for AI enabled RAN optimisation | CMCC |
| R3-206875 | CB: # 27_EnhDataColl_StdImpact - Summary of email discussion | Samsung - moderator |
| 20.1 | General | |
| R3-205910 | Support Non-Terrestrial Networks | Huawei Tech.(UK) Co., Ltd |
| R3-206349 | NR_NTN_solutions work plan | THALES |
| R3-206597 | (TP for BL CR TS 38.300) NTN Stage 2 completion | Huawei, Thales, CATT, ZTE |
| R3-206843 | LS on signalling of satellite backhaul connection | SA WG2 |
| R3-206860 | CB: # 17_NTNgeneral_and_LS - Summary of email discussion | Huawei - moderator |
| R3-207022 | (TP for BL CR TS 38.300) NTN Stage 2 completion | Huawei, Thales, CATT, ZTE |
| R3-207023 | Reply LS on LS on signalling of satellite backhaul connection | Huawei |
| R3-207060 | Reply LS on LS on signalling of satellite backhaul connection | Huawei |
| R3-207061 | (TP for BL CR TS 38.300) NTN Stage 2 completion | Huawei, Thales, CATT, ZTE |
| R3-207246 | BLCR to 38.300_NR Non-Terrestrial Networks | Huawil |
| R3-207248 | Support Non-Terrestrial Networks | Huawei |
| 20.2.1 | Network Identifier Handling | |
| R3-205940 | NR-NTN: Network Identities Handling | Fraunhofer IIS, Fraunhofer HHI |
| R3-206261 | Handling of cell identity signalling towards the CN | Qualcomm Incorporated |
| R3-206262 | [DRAFT] Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Qualcomm Incorporated |
| R3-206263 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated |
| R3-206264 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated |
| R3-206275 | Discussion on identifier handling in NTN | CATT |
| R3-206381 | Network Identifier Handling for moving cells | Ericsson |
| R3-206400 | On Cell id in User Location Information | Intel Corporation |
| R3-206842 | Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | SA WG2 |
| R3-206861 | CB: # 18_NTN_IDhandling - Summary of email discussion | Ericsson, Qualcomm - moderator |
| R3-207013 | [DRAFT] LS to SA2, RAN2 | Qualcomm |
| R3-207062 | Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Qualcomm |
| 20.2.2 | Registration Update and Paging Handling | |
| R3-206044 | Discussion on paging UE per SSB beam in NTN cell | Samsung |
| R3-206045 | CR to 38413 for paging UE per SSB beam in NTN cell | Samsung |
| R3-206046 | CR to 38473 for paging UE per SSB beam in NTN cell | Samsung |
| R3-206276 | Discussion on potential paging enhancement for NTN | CATT |
| R3-206277 | Support of UE location based Paging for NTN | CATT |
| R3-206382 | Handling of Registration and Paging with moving cells | Ericsson |
| R3-206599 | Some consideration on RAN3 agreements | Huawei |
| R3-206686 | Further Discussion on Paging Enhancement for NTN | ZTE |
| R3-206862 | CB: # 23_NTN_RegUpdate_and_Paging - Summary of email discussion | Huawei - moderator |
| 20.2.3 | Cell Relation Handling | |
| R3-206600 | Cell management enhancement for NTN | Huawei |
| R3-206685 | Further Discussion on Cell Relation for NTN | ZTE |
| R3-206863 | CB: # 21_NTN_CellRelation - Summary of email discussion | ZTE - moderator |
| 20.2.4 | Feeder Link Switch-Over for LEO | |
| R3-205964 | On Feeder link Switch | InterDigital |
| R3-206057 | Discussion on enhancements for feeder link switch over | Samsung |
| R3-206068 | Discussion on feeder link switch over | China Telecommunications |
| R3-206278 | Discussion on feederlink switch | CATT |
| R3-206279 | (TP for NR BL CR for TS 38.300) Support of feeder link switch | CATT |
| R3-206291 | Discussion on Feeder Link Switch | Nokia, Nokia Shanghai Bell |
| R3-206347 | NR-NTN: Feeder link switch over | THALES |
| R3-206401 | On Feeder Link Switch | Intel Corporation |
| R3-206404 | Feeder Link Switchover Support | Ericsson LM |
| R3-206405 | Support for Feeder Link Switchover for Transparent Architecture | Ericsson LM |
| R3-206598 | Discussion on feeder link switch for NTN | Huawei |
| R3-206687 | Further Discussion on LEO Feeder Link Switch-over | ZTE |
| R3-206801 | Feeder link switch for NTN | CMCC |
| R3-206864 | CB: # 22_NTNfeederLinkSwitch - Summary of email discussion | Thales - moderator |
| R3-207063 | CB: # 22_NTNfeederLinkSwitch - Summary of email discussion | Thales - moderator |
| R3-207064 | Feeder link switch: St2 TP to BL CR to 38.300 | Thales |
| 20.2.5 | Aspects Related to Country-Specific Routing | |
| R3-206067 | Discussion on Country-Specific Routing issue | China Telecommunications |
| R3-206265 | Discussion of scenarios for country specific routing | Qualcomm Incorporated |
| R3-206266 | Clarification of NAS Node Selection Function | Qualcomm Incorporated |
| R3-206865 | CB: # 20_NTNcountry_specific_routing - Summary of email discussion | China Telecom, Qualcomm - moderator |
| 20.2.6 | Others | |
| R3-206406 | Observations on Xn Usage for Transparent NTN | Ericsson LM |
| R3-206866 | CB: # 19_NTN_Xn_usage - Summary of email discussion | Ericsson - moderator |
| 22.1 | General | |
| R3-205907 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-205909 | Introduction of NR MBS | Huawei, CMCC |
| R3-205962 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-206312 | Introduction of MBS(BL CR for 38.463) | CATT |
| R3-206383 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-206408 | (TP to TS 38.300 BL CR) Inclusion of the agreements of RAN3#109 | Huawei |
| R3-206409 | (TP to TS 38.401 BL CR) Inclusion of the agreements of RAN3#109 | Huawei |
| R3-206484 | Introduction of NR MBS | Lenovo, Motorola Mobility |
| R3-206526 | MBS BL CR for TS38.410 | ZTE |
| R3-206904 | CB: # 28_MBS_general - Summary of email discussion | Huawei - moderator |
| R3-207045 | (TP to TS 38.300 BL CR) Inclusion of the agreements of RAN3#109 | Huawei |
| R3-207046 | (TP to TS 38.401 BL CR) Inclusion of the agreements of RAN3#109 | Huawei |
| R3-207049 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-207050 | Introduction of NR MBS | Lenovo, Motorola mobility |
| R3-207051 | MBS BL CR for TS38.410 | ZTE |
| R3-207052 | Introduction of NR MBS | Huawei, CMCC |
| R3-207249 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-207250 | MBS BL CR for TS38.410 | ZTE |
| R3-207251 | Introduction of NR MBS | Huawei, CMCC |
| 22.2.1 | General Architecture | |
| R3-205925 | LS on RAN impact of FS_5MBS Study | SA WG2 |
| R3-205971 | RAN impact of FS_5MBS Study | Nokia, Nokia Shanghai Bell |
| R3-205972 | Response LS on RAN impact of FS_5MBS Study | Nokia, Nokia Shanghai Bell |
| R3-205982 | Discussion on NR MBS architecutre | CHENGDU TD TECH LTD. |
| R3-206244 | Enhancement to NG-RAN architecture for MBS | Nokia, Nokia Shanghai Bell |
| R3-206306 | Some Issues on Architecture of MBS | CATT |
| R3-206384 | [TP for BL CR 38.300/38.401] Capturing agreements on NG-RAN architecture for 5G MBS | Ericsson |
| R3-206410 | [DRAFT] Reply LS on LS on RAN impact of FS_5MBS Study | Huawei |
| R3-206483 | Provisioning of Broadcast Services in RAN | Lenovo, Motorola Mobility |
| R3-206485 | Shared Delivery over F1-U for 5G MBS | Lenovo, Motorola Mobility |
| R3-206537 | Discussion on the MBS LS from SA2 (S2-2006044) | Ericsson |
| R3-206538 | [DRAFT] Reply LS on RAN impact of FS_5MBS Study | Ericsson |
| R3-206539 | Discussion on feedback for support of broadcast in Rel-17 from SA/RAN#89 in SP-200884 and RP-202086 | Ericsson |
| R3-206784 | On NG-RAN Architecture for 5G MBS | CMCC |
| R3-206906 | CB: # 57_MBS_LSs - Summary of email discussion | Nokia - moderator |
| R3-206907 | CB: # 58_MBSarch - Summary of email discussion | Ericsson - moderator |
| R3-207039 | Response LS on RAN impact of FS_5MBS Study | Nokia, Nokia Shanghai Bell |
| R3-207059 | Response LS on RAN impact of FS_5MBS Study | Nokia, Nokia Shanghai Bell |
| 22.2.2 | Session Management over NG | |
| R3-206031 | TP for MBS BLCR for 38.413-Session Management over NG | Samsung |
| R3-206176 | Session management procedure | Qualcomm Incorporated |
| R3-206245 | MBS Stage 2 for Session management | Nokia, Nokia Shanghai Bell |
| R3-206247 | MBS Session management for joining/leaving | Nokia, Nokia Shanghai Bell |
| R3-206248 | MBS Session Management for NG-U resources setup | Nokia, Nokia Shanghai Bell |
| R3-206310 | Discussion on NG session management | CATT,CBN |
| R3-206311 | Draft LS to SA2 on multicast service area | CATT |
| R3-206385 | [TP for BL CR 38.300] Session Management for NR MBS | Ericsson |
| R3-206386 | [TP for NGAP BL CR] - MBS Session Resource Management for NR MBS | Ericsson |
| R3-206411 | (TP to TS 38.410 BL CR) Session Management over NGAP | Huawei |
| R3-206486 | MBS Session Management over NG interface | Lenovo, Motorola Mobility |
| R3-206527 | Discussion on MBS session management | ZTE |
| R3-206785 | Session management over NG interface | CMCC |
| R3-206908 | CB: # 59_MBSsessionMgmt_NG - Summary of email discussion | Nokia - moderator |
| R3-207058 | CB: # 59_MBSsessionMgmt_NG - Summary of email discussion | Nokia - moderator |
| 22.2.3 | Dynamic Change Between PTP and PTM for UEs in RRC_CONNECTED State | |
| R3-206029 | Dynamic Change Between PTP and PTM | Samsung |
| R3-206058 | Dynamic switch between PTM and PTP for RRC_CONNECTED UE | CHENGDU TD TECH LTD. |
| R3-206207 | MBS assistance information | Intel Deutschland GmbH |
| R3-206250 | MBS Stage 2 for PTP-PTM Switching | Nokia, Nokia Shanghai Bell |
| R3-206299 | Discussion on dynamic change between PTM and PTP | CATT |
| R3-206387 | [TP for BL CR 38.300] Further Aspects of Dynamic PTP/PTM change for RRC_CONNECTED Ues | Ericsson |
| R3-206412 | (TP to TS 38.401 BL CR) Decision on PTP and PTM | Huawei |
| R3-206487 | Configuration and Dynamic switch between PTP and PTM | Lenovo, Motorola Mobility |
| R3-206528 | Dynamic mode switching for NR MBS | ZTE |
| R3-206650 | Issues on dynamic change between PTP and PTM | LG Electronics |
| R3-206909 | CB: # 60_MBS_PTP-PTMdynChg - Summary of email discussion7040 | Nokia - moderator |
| R3-207040 | MBS Stage 2 for PTP-PTM Switching | Nokia, Nokia Shanghai Bell |
| R3-207055 | MBS Stage 2 for PTP-PTM Switching | Nokia, Nokia Shanghai Bell |
| 22.2.4 | Bearer Management over F1/E1 | |
| R3-206027 | MBS bearer setup in F1 and E1 | Samsung |
| R3-206028 | TP for MBS BLCR for 38.473-Addition of MBS feature | Samsung |
| R3-206308 | Consideration on MBS context management over F1 and E1 | CATT |
| R3-206388 | On F1/E1 bearer management aspects | Ericsson |
| R3-206413 | (TP to TS 38.401 BL CR) Bearer management over F1 and E1 | Huawei |
| R3-206414 | (TP to TS 38.470 BL CR) Bearer management over F1 interface | Huawei |
| R3-206415 | (TP to TS 38.460 BL CR) Bearer management over E1 interface | Huawei |
| R3-206529 | Bearer Management for NR MBS | ZTE |
| R3-206835 | Consideration on MBS context management over F1 and E1 | CATT |
| R3-206910 | CB: # 61_MBS_F1-E1bearerMgmt - Summary of email discussion | Huawei - moderator |
| R3-207056 | (TP to TS 38.401 BL CR) Bearer management over F1 and E1 | Huawei |
| 22.2.5 | Others | |
| R3-206307 | Consideration on MBS Transmission Area | CATT |
| R3-206389 | On 5G MBS Service Area | Ericsson |
| R3-206488 | 5G MBS Transmission Mode and Area Control within NG-RAN | Lenovo, Motorola Mobility |
| R3-206530 | Discussion on multicast & broadcast transmission area | ZTE |
| R3-206776 | Consideration on Dynamic Control of the Broadcast/Multicast Transmission Area | LG Electronics |
| R3-206911 | CB: # 62_MBSarch_TransmissionArea - Summary of email discussion | ZTE - moderator |
| 22.3.1 | Mobility Between MBS Supporting Nodes | |
| R3-206030 | Mobility Between MBS Supporting Nodes | Samsung |
| R3-206059 | Mobility between MBS supporting nodes | CHENGDU TD TECH LTD. |
| R3-206177 | Loss-less handover procedure for NR multicast | Qualcomm Incorporated |
| R3-206251 | MBS to MBS Mobility Key Principles | Nokia, Nokia Shanghai Bell |
| R3-206252 | MBS Stage 2 for Mobility Management | Nokia, Nokia Shanghai Bell |
| R3-206253 | MBS Mobility Control Plane | Nokia, Nokia Shanghai Bell |
| R3-206254 | Support of MBS Seamless Mobility | Nokia, Nokia Shanghai Bell |
| R3-206300 | Discussion on general principle for MBS service continuity | CATT |
| R3-206301 | Possible solutions to minimise data loss | CATT |
| R3-206302 | TP on TS 38.300 on MBS service continuity | CATT |
| R3-206303 | Draft LS on MBS service continuity | CATT |
| R3-206390 | Minimization of data loss at mobility between MBS supporting nodes | Ericsson |
| R3-206391 | [TP for BL CR 38.413] Session control for Xn and NG based mobility | Ericsson |
| R3-206392 | [TP for BL CR XnAP] Session Control for Xn mobility | Ericsson |
| R3-206416 | (TP to TS 38.300 BL CR) Mobility procedure between MBS supporting nodes | Huawei |
| R3-206417 | (TP to TS 38.401 BL CR) Mobility procedure between MBS supporting nodes | Huawei |
| R3-206418 | Minimize Data Loss during Mobility between MBS supporting nodes | Huawei |
| R3-206419 | [DRAFT] LS on minimizing data loss during MBS mobility | Huawei |
| R3-206489 | PDCP Count Value Synchronization and Data Forwarding | Lenovo, Motorola Mobility |
| R3-206531 | Consideration on MBS mobility procedure | ZTE |
| R3-206532 | Consideration on lossless handover for NR MBS | ZTE |
| R3-206747 | Consideration on Bearer Type Change for MBS Mobility | LG Electronics |
| R3-206802 | Discussion on Mobility with Service continuity | CMCC |
| R3-206912 | CB: # 63_MBSmobility_supporting_nodes - Summary of email discussion | Ericsson - moderator |
| R3-207006 | MBS Stage 2 for Mobility Management | Nokia, Nokia Shanghai Bell |
| R3-207057 | MBS Stage 2 for Mobility Management | Nokia, Nokia Shanghai Bell |
| 22.3.2 | Mobility Between MBS Supporting and non-MBS Supporting Nodes | |
| R3-206060 | Mobility between an MBS supporting node and a NON-MBS supporting node | CHENGDU TD TECH LTD. |
| R3-206304 | Minimising data loss on handover from non-MBS gNB toward MBS gNB | CATT |
| R3-206305 | Service continuity from MBS gNB toward non-MBS gNB | CATT |
| R3-206393 | Session control for Xn and NG based mobility - interworking with NG-RAN nodes not supporting MBS | Ericsson |
| R3-206394 | [TP for BL CR 38.413] Session control for Xn based mobility - interworking with NG-RAN nodes not supporting MBS | Ericsson |
| R3-206420 | Mobility between MBS supporting and non-supporting nodes | Huawei |
| R3-206533 | Discussion on UE mobility between an MBS-supporting gNB and a non-MBS-supporting gNB | ZTE |
| R3-206913 | CB: # 64_MBSmobility_non-supporting_nodes - Summary of email discussion | ZTE - moderator |
| R3-207053 | CB: # 64_MBSmobility_non-supporting_nodes - Summary of email discussion | ZTE - moderator |
| R3-207161 | CB: # 64_MBSmobility_non-supporting_nodes - Summary of email discussion | ZTE - moderator |
| 22.3.3 | Others | |
| R3-206395 | Further aspects for Session control signalling design - Dual Connectivity | Ericsson |
| R3-206490 | Support CHO for NR MBS with Service Continuity | Lenovo, Motorola Mobility |
| R3-206556 | Discussion on support of reliable and low-latency NR multicast mobility | TCL Communication Ltd. |
| R3-206914 | CB: # 65_MBSmobility_AOB - Summary of email discussion | Lenovo - moderato |
| 22.4 | Others | |
| R3-206309 | MBS reception of Idle and In-active Ues | CATT |
| R3-206396 | IDLE and INACTIVE Support for NR MBS | Ericsson |
| R3-206421 | (TP to TS 38.410 BL CR) Support of Broadcast in NR MBS | Huawei |
| R3-206534 | Discussion on Broadcast service continuity in NR MBS | ZTE |
| R3-206915 | CB: # 66_MBS_AOB - Summary of email discussion | CATT - moderator |
| R3-207054 | (TP to TS 38.410 BL CR) Support of Broadcast in NR MBS | Huawei |
| R3-207160 | CB: # 66_MBS_AOB - Summary of email discussion | CATT - moderator |